Online car-hailing travel processing method and device, electronic equipment, storage medium and program product

Abstract

The invention provides an online car-hailing travel processing method and device, electronic equipment, a computer readable storage medium and a computer program product, and relates to the technical field of computers, the field of Internet of Vehicles and the technical field of artificial intelligence, and the method comprises the steps: responding to the ending of the online car-hailing travel, and displaying an appeal entrance for the online car-hailing travel; in response to a trigger operation for the appeal entrance, displaying an appeal determination interface which is used for determining the fee of the online car-hailing travel; wherein the appeal determination interface comprises a negative control, and the negative control is used for indicating the fee of the negative online car-hailing travel; in response to a triggering operation aiming at the negative control, when the online car-hailing travel meets a first fee exempting condition, displaying fee exempting information; wherein the expense removal information is used for indicating that at least part of expense of the online car-hailing travel is removed. According to the invention, the efficiency of processing the online car-hailing travel can be improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing ride-hailing trips. Background Technology

[0002] In related technologies, if a passenger complains about the fare for a ride-hailing trip, they must first fill out a complaint reason and then go through a series of complaint procedures before the fare can be waived. This makes the complaint process for ride-hailing trip fares cumbersome, resulting in low efficiency in handling such cases. Summary of the Invention

[0003] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing ride-hailing trips, which can improve the efficiency of processing ride-hailing trips.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a method for processing ride-hailing trips, including:

[0006] In response to the termination of the ride-hailing trip, an appeal portal for the ride-hailing trip is displayed;

[0007] In response to a trigger operation on the appeal entry point, an appeal confirmation interface is displayed, which is used to confirm the cost of the ride-hailing trip.

[0008] The appeal confirmation interface includes a denial control, which is used to indicate whether the fare for the ride-hailing trip is denied.

[0009] In response to the triggering operation of the negative control, when the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed;

[0010] The fee waiver information is used to indicate that at least a portion of the fare for the ride-hailing trip has been waived.

[0011] This application provides a device for processing ride-hailing trips, including:

[0012] The first display module is used to display an appeal portal for the ride-hailing trip in response to the termination of the ride-hailing trip;

[0013] The second display module is used to display an appeal confirmation interface in response to a trigger operation on the appeal entry point. The appeal confirmation interface is used to confirm the fare for the ride-hailing trip. The appeal confirmation interface includes a negation control, which is used to indicate that the fare for the ride-hailing trip is denied.

[0014] The third display module is used to respond to the triggering operation of the negative control and display fee exemption information when the ride-hailing trip meets the first fee exemption condition; wherein the fee exemption information is used to indicate that at least part of the fee for the ride-hailing trip has been exempted.

[0015] In the above scheme, the first display module is further configured to display a payment confirmation interface in response to the end of the ride-hailing trip. The payment confirmation interface is used to instruct the user to confirm and pay the fare for the ride-hailing trip. The payment confirmation interface displays an appeal entry for the ride-hailing trip.

[0016] In the above scheme, the payment method for the ride-hailing trip is automatic payment, the appeal entry is displayed on the payment confirmation interface, and the device further includes a fourth display module, which is used to display a countdown on the payment confirmation interface; wherein, the countdown is used to indicate the remaining time for payment of the ride-hailing trip fare; the first display module is also used to display the appeal confirmation interface in response to a trigger operation on the appeal entry when the countdown has not ended.

[0017] In the above scheme, the device further includes a fifth display module, which is used to display a payment success interface when the countdown ends and no trigger operation is received for the appeal entry; wherein, the payment success interface is used to indicate that the fare for the ride-hailing trip has been paid.

[0018] In the above scheme, the device further includes an acquisition module, which is used to acquire the trip information of the ride-hailing trip; the fourth display module is also used to display the countdown on the payment confirmation interface when the trip information indicates that the cost of the ride-hailing trip is abnormal.

[0019] In the above scheme, the first display module is further configured to display a payment success interface in response to the termination of the ride-hailing trip and the payment of the ride-hailing trip; wherein, the payment success interface is used to indicate that the payment of the ride-hailing trip has been made; and the payment success interface displays an appeal entry for the ride-hailing trip.

[0020] In the above scheme, the third display module is further configured to detect the ride-hailing trip in response to the trigger operation of the negative control and obtain a detection result; wherein, the detection result is used to indicate whether the ride-hailing trip meets the first fee exemption condition; when the detection result indicates that the ride-hailing trip meets the first fee exemption condition, fee exemption information is displayed.

[0021] In the above scheme, the first fee waiver condition includes a first waiver condition, which indicates that the reason for the abnormality in the fare of the ride-hailing trip is related to the driver of the ride-hailing trip; the third display module is further configured to respond to the trigger operation of the negative control, and when the ride-hailing trip meets the first waiver condition and the fare of the ride-hailing trip has not yet been paid, display the first fee waiver information; wherein, the first fee waiver information is used to indicate that at least part of the fare of the ride-hailing trip has been waived.

[0022] In the above scheme, the first fee waiver condition includes a first waiver condition, which indicates that the reason for the abnormality in the fare of the ride-hailing trip is the driver of the ride-hailing trip; the third display module is also used to respond to the trigger operation of the negative control, and when the ride-hailing trip meets the first waiver condition and the fare of the ride-hailing trip has been paid, display second fee waiver information; wherein, the second fee waiver information is used to indicate that at least part of the fare of the ride-hailing trip has been refunded.

[0023] In the above scheme, the first fee waiver condition includes a second waiver condition, which indicates that the reason for the abnormal fare of the ride-hailing trip is related to the driver of the ride-hailing trip; the third display module is further configured to respond to the triggering operation of the negation control, and when the ride-hailing trip meets the second waiver condition, display a negation reason submission interface; wherein, the negation reason submission interface is used to input and submit the reason for negating the fare of the ride-hailing trip; in response to the negation reason submitted based on the negation reason submission interface, display third fee waiver information; wherein, the third fee waiver information is used to indicate that at least part of the fare of the ride-hailing trip is temporarily waived.

[0024] In the above scheme, the device further includes a submission module, which is used to display the input negative reason on the negative reason submission interface in response to an input operation on the negative reason submission interface; display a submission control for submitting the negative reason input based on the negative reason submission interface; and receive the negative reason submitted based on the negative reason submission interface in response to a trigger operation on the submission control.

[0025] In the above scheme, the device further includes a sixth display module, which is used to display explanatory information in response to a triggering operation for the third fee waiver information; wherein the explanatory information is used to explain the process of temporarily waiving at least a portion of the fare for the ride-hailing trip indicated by the third fee waiver information.

[0026] In the above scheme, the device further includes a seventh display module, which is used to display processing prompt information in response to the negative reason submitted based on the negative reason submission interface; wherein the processing prompt information is used to indicate the processing status of the fare of the ride-hailing trip.

[0027] In the above scheme, the device further includes an eighth display module, which is used to display a confirmation control on the appeal confirmation interface, the confirmation control being used to determine the cost of the ride-hailing trip; and to display a payment success interface in response to a trigger operation on the confirmation control; wherein the payment success interface is used to indicate that the cost of the ride-hailing trip has been paid.

[0028] In the above scheme, the fee waiver information includes third fee waiver information, which is used to indicate that at least part of the fare for the ride-hailing trip is temporarily waived; the device also includes a ninth display module, which is used to display the ride-hailing trip creation interface in response to the display operation of the ride-hailing trip creation interface; in response to the trip creation operation triggered based on the creation interface, if the fare for the ride-hailing trip has not yet been paid, a new ride-hailing trip is created.

[0029] In the above scheme, the device further includes a tenth display module, which is used to display a first prompt message when the ride-hailing trip does not meet the second fee exemption conditions, and to switch the display of the third fee exemption information to the display of payment success information; wherein, the first prompt message is used to indicate that the ride-hailing trip does not meet the second fee exemption conditions and that the fare of the ride-hailing trip needs to be paid, and the payment success information is used to indicate that the fare of the ride-hailing trip has been paid.

[0030] In the above scheme, the device further includes an eleventh display module, which is used to respond to the triggering operation of the negative control, and when the ride-hailing trip meets the second fee exemption condition, display a second prompt message, and switch the display of the third fee exemption information to the display of the target fee exemption information; wherein, the second prompt message is used to indicate that the ride-hailing trip meets the second fee exemption condition and that at least part of the fare of the ride-hailing trip does not need to be paid, and the target fee exemption information is used to indicate that at least part of the fare of the ride-hailing trip has been exempted.

[0031] This application provides an electronic device, including:

[0032] Memory, used to store executable instructions;

[0033] The processor, when executing executable instructions stored in the memory, implements the ride-hailing trip processing method provided in the embodiments of this application.

[0034] This application provides a computer-readable storage medium storing executable instructions for inducing a processor to execute and implement the ride-hailing trip processing method provided in this application.

[0035] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the ride-hailing trip processing method provided in this application.

[0036] The embodiments of this application have the following beneficial effects:

[0037] At the end of the ride-hailing trip, an appeal portal for the trip is directly displayed. Upon receiving a trigger action on this portal, an appeal confirmation screen is displayed. This responds to trigger actions on the negation control within the confirmation screen. If the trip meets the first fare waiver condition, fare waiver information is displayed. Thus, if a passenger disagrees with the fare, they can directly appeal based on the negation control on the confirmation screen. Compared to the cumbersome complaint process for ride-hailing trips in related technologies, this significantly improves the efficiency of handling ride-hailing trips. Attached Figure Description

[0038] Figure 1 This is a schematic diagram of the architecture of the ride-hailing trip processing system provided in the embodiments of this application;

[0039] Figure 2This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application;

[0040] Figure 3 This is a flowchart illustrating the method for processing ride-hailing trips provided in an embodiment of this application;

[0041] Figure 4 This is a first schematic diagram of the payment confirmation interface provided in the embodiments of this application;

[0042] Figure 5 This is a second schematic diagram of the payment confirmation interface provided in the embodiments of this application;

[0043] Figure 6 This is a schematic diagram of the payment success interface provided in an embodiment of this application;

[0044] Figure 7 This is a schematic diagram showing the appeal entry point provided in this application embodiment displayed on the payment success screen;

[0045] Figure 8 This is a schematic diagram of the appeal determination interface provided in an embodiment of this application;

[0046] Figure 9 This is a schematic diagram of the first fee waiver information provided in the embodiments of this application;

[0047] Figure 10 This is a schematic diagram of the second fee exemption information provided in the embodiments of this application;

[0048] Figure 11 This is a schematic diagram of the third fee exemption information provided in the embodiments of this application;

[0049] Figure 12 This is a schematic diagram of the negative reason submission interface provided in an embodiment of this application;

[0050] Figure 13 This is a schematic diagram of the submission success message provided in an embodiment of this application;

[0051] Figure 14 This is a schematic diagram illustrating the explanatory information provided in the embodiments of this application;

[0052] Figure 15 This is a schematic diagram of the processing prompt information provided in the embodiments of this application;

[0053] Figure 16 This is a schematic diagram illustrating the process when a ride-hailing trip does not meet the second fee waiver conditions, as provided in the embodiments of this application.

[0054] Figure 17 This is a schematic diagram illustrating the process when a ride-hailing trip meets the second fare exemption condition, as provided in an embodiment of this application.

[0055] Figure 18 This is a flowchart of the scheme for determining liability between drivers and passengers in ride-hailing services where passengers do not ride, as provided in this application embodiment;

[0056] Figure 19 This is a schematic diagram illustrating the process of determining driver liability provided in an embodiment of this application;

[0057] Figure 20 This is a schematic diagram illustrating the process in which the driver is likely at fault, as provided in the embodiments of this application;

[0058] Figure 21 This is a first technical architecture diagram of the scheme for determining the liability of drivers and passengers who fail to ride in a ride-hailing service, as provided in the embodiments of this application.

[0059] Figure 22 This is the second technical architecture diagram of the scheme for determining the liability of drivers and passengers who fail to ride in a ride-hailing service, as provided in the embodiments of this application. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0061] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0062] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0063] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0064] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0065] 1) Client, also known as user terminal, refers to the program that provides local services to users in contrast to the server. Except for some applications that can only run locally, it is generally installed on ordinary terminals and needs to work in conjunction with the server. That is, there needs to be a corresponding server and service program in the network to provide the corresponding services. Thus, a specific communication connection needs to be established between the client and the server to ensure the normal operation of the application, such as an autonomous driving client (such as a map navigation client).

[0066] 2) Ride-hailing trip, used to indicate the planned route from the origin to the destination based on ride-hailing.

[0067] 3) Trip information, including at least one of the following: trip cost, trip start time, trip estimated end time, trip origin, trip destination, and trip status information; wherein, the trip status information includes at least the current location information of the object corresponding to the trip, the distance of the current location of the object corresponding to the trip from the destination, and the current state of the object corresponding to the trip, such as stationary or moving.

[0068] 4) Gradient Boosting Decision Tree Algorithm (XGBoost, Xtreme Gradient Boosting): An efficient gradient boosting decision tree algorithm with advantages such as high accuracy, low overfitting risk, and high robustness.

[0069] In some embodiments, see Figure 1 , Figure 1 This is a schematic diagram of the architecture of the ride-hailing trip processing system 100 provided in this application embodiment. To realize the application scenario of ride-hailing trip processing (for example, if a passenger is charged even though they did not take the ride, after the ride-hailing trip ends, an appeal entry for the ride-hailing trip is displayed on the payment interface, and then in response to the triggering operation of the appeal entry, an appeal confirmation interface including a disapproval control is displayed, thereby responding to the triggering operation of the disapproval control, when the responsibility for the charge for not taking the ride lies with the driver or is likely to lie with the driver, information indicating that the fare for the ride-hailing trip has been waived is displayed), a ride-hailing trip processing client 401 is set on the terminal (terminal 400 is shown as an example). The display interface (display interface 401-1 is shown as an example) shows that the terminal 400 is connected to the server 200 through the network 300, wherein the network 300 can be a wide area network or a local area network, or a combination of both, and data transmission is achieved using a wireless or wired link.

[0070] Server 200 is used to send an end message indicating the end of the ride-hailing trip to terminal 400;

[0071] Terminal 400 is used to receive end information sent by server 200, and in response to ending the ride-hailing trip, display an appeal entry for the ride-hailing trip; in response to a trigger operation on the appeal entry, display an appeal confirmation interface, which is used to confirm the fare of the ride-hailing trip; wherein, the appeal confirmation interface includes a negation control, which is used to indicate the negation of the fare of the ride-hailing trip; in response to a trigger operation on the negation control, when the ride-hailing trip meets the first fare waiver condition, display fare waiver information; wherein, the fare waiver information is used to indicate that at least part of the fare of the ride-hailing trip has been waived.

[0072] In some embodiments, server 200 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. Terminal 400 can be a smartphone, tablet, laptop, desktop computer, set-top box, smart voice interaction device, smart home appliance, vehicle terminal, aircraft, portable music player, personal digital assistant, dedicated messaging device, portable gaming device, smart speaker, and smartwatch, but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, which is not limited in this embodiment.

[0073] The electronic device that implements the ride-hailing trip processing method provided in the embodiments of this application will now be described. See also Figure 2 , Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device can be a server or a terminal. The electronic device is used as an example. Figure 1 Taking the terminal shown as an example, Figure 2 The illustrated electronic device includes at least one processor 410, a memory 450, at least one network interface 420, and a user interface 430. The various components in terminal 400 are coupled together via a bus system 440. It is understood that the bus system 440 is used to implement communication between these components. In addition to a data bus, the bus system 440 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 3 The general labeled all buses as Bus System 440.

[0074] The processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0075] User interface 430 includes one or more output devices 431 that enable the display of media content, including one or more speakers and / or one or more visual displays. User interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0076] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices physically located away from the processor 410.

[0077] The memory 450 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450 described in this application embodiment is intended to include any suitable type of memory.

[0078] In some embodiments, memory 450 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0079] Operating system 451 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0080] The network communication module 452 is used to reach other electronic devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc.

[0081] Presentation module 453 is configured to enable the display of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 (e.g., a display screen, a speaker, etc.) associated with user interface 430;

[0082] The input processing module 454 is used to detect and translate one or more user inputs or interactions from one or more input devices 432.

[0083] In some embodiments, the apparatus provided in this application can be implemented in software. Figure 2 A processing device 455 for ride-hailing trips stored in memory 450 is shown. This device can be software in the form of programs and plug-ins, including the following software modules: a first display module 4551, a second display module 4552, and a third display module 4553. These modules are logically integrated and can therefore be arbitrarily combined or further separated according to their implemented functions. The functions of each module will be described below.

[0084] In other embodiments, the apparatus provided in this application can be implemented in hardware. As an example, the ride-hailing trip processing apparatus provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the ride-hailing trip processing method provided in this application. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0085] In some embodiments, the terminal or server can implement the ride-hailing trip processing method provided in this application by running a computer program. For example, the computer program can be a native program or software module in an operating system; it can be a native application (APP), that is, a program that needs to be installed in the operating system to run, such as an instant messaging APP or a web browser APP; it can also be a mini-program, that is, a program that only needs to be downloaded into a browser environment to run; or it can be a mini-program that can be embedded in any APP. In short, the above-mentioned computer program can be any form of application, module, or plugin.

[0086] Based on the above description of the ride-hailing trip processing system and electronic device provided in the embodiments of this application, the ride-hailing trip processing method provided in the embodiments of this application is described below. In actual implementation, the ride-hailing trip processing method provided in the embodiments of this application can be implemented by the terminal or the server alone, or by the terminal and the server working together, so that... Figure 1 The following description uses the terminal 400 in the embodiment of the present invention to illustrate the method for processing ride-hailing trips independently. See also... Figure 3 , Figure 3 This is a flowchart illustrating the method for processing ride-hailing trips provided in this application embodiment, which will be combined with... Figure 3 The steps shown are explained.

[0087] Step 101: The terminal responds by ending the ride-hailing trip and displays the appeal portal for the ride-hailing trip.

[0088] In practice, the appeal entry point can be a control or a text link, etc., and this application embodiment does not limit this. After a ride-hailing trip ends, there are multiple ways to display the appeal entry point for the ride-hailing trip. For example, the appeal entry point for the ride-hailing trip can be on the payment confirmation screen when the ride-hailing trip has not been paid, or on the payment success screen after the ride-hailing trip has been paid. This application embodiment does not limit this. Next, the different methods of displaying the appeal entry point for the ride-hailing trip will be described separately.

[0089] In some embodiments, when the appeal portal is displayed on the payment confirmation screen when the ride-hailing trip is not paid, the process of displaying the appeal portal for the ride-hailing trip in response to ending the ride-hailing trip may be as follows: in response to ending the ride-hailing trip, a payment confirmation screen is displayed, which is used to instruct the user to confirm and pay the fare for the ride-hailing trip; and on the payment confirmation screen, the appeal portal for the ride-hailing trip is displayed.

[0090] It should be noted that there are two payment methods for ride-hailing trips: automatic payment and manual payment. Automatic payment means that the fare for the ride-hailing trip is automatically deducted after each trip ends, while manual payment means that after each ride-hailing trip ends, a bill is sent to the passenger, allowing the passenger to pay the fare themselves after confirming the bill.

[0091] As an example, when the payment method for a ride-hailing trip is manual payment, the payment confirmation screen is displayed directly upon ending the ride-hailing trip. See [link to relevant documentation]. Figure 4 , Figure 4 This is a first schematic diagram of the payment confirmation interface provided in the embodiments of this application, based on Figure 4 In response to ending the ride-hailing trip, the following message will be displayed: Figure 4The payment confirmation screen is shown, and then the appeal portal for the ride-hailing trip is displayed as indicated by the dashed box 401.

[0092] As another example, when the payment method for a ride-hailing trip is automatic payment, a countdown will be displayed on the payment confirmation screen in response to the end of the ride-hailing trip. The countdown is used to indicate the remaining time for payment of the ride-hailing trip fee. The process of displaying the appeal confirmation screen in response to the triggering operation of the appeal portal can be as follows: the appeal confirmation screen is displayed in response to the triggering operation of the appeal portal before the countdown ends.

[0093] For example, see Figure 5 , Figure 5 This is a second schematic diagram of the payment confirmation interface provided in the embodiments of this application, based on Figure 5 In response to ending the ride-hailing trip, the following message will be displayed: Figure 5 The payment confirmation screen is shown. Then, on the payment confirmation screen, a countdown as indicated by 501 and an appeal entry as indicated by the dashed box 502 are displayed. Thus, when the countdown has not ended, in response to the triggering operation of the appeal entry, the appeal confirmation screen is displayed.

[0094] The countdown time can be preset, for example, 5 minutes, to help passengers decide whether to file a complaint regarding the ride-hailing trip.

[0095] In practice, if automatic payment is set, the fare for the ride-hailing trip will be automatically deducted after the trip ends. However, in this embodiment, when automatic payment is set and the ride-hailing trip ends, the trip information is obtained. Thus, the countdown process displayed on the payment confirmation interface can be such that when the trip information indicates an abnormality in the fare for the ride-hailing trip, the countdown is displayed on the payment confirmation interface.

[0096] It should be noted that the trip information includes the cost, route, and duration of the ride-hailing trip. After obtaining the trip information, the ride-hailing trip is checked based on the trip information to obtain the check results. The check results are used to indicate whether there are any abnormalities in the cost of the corresponding ride-hailing trip. Therefore, when the trip information indicates that the cost of the ride-hailing trip is abnormal, a countdown will be displayed on the payment confirmation interface. That is, when the cost check results indicate that the cost of the ride-hailing trip is abnormal, a countdown will be displayed on the payment confirmation interface.

[0097] It should be noted that the trip information can be obtained from the server side. For example, after the ride-hailing trip ends, the terminal sends a trip information retrieval request to the server, so that the server sends the ride-hailing trip information to the terminal based on the request. The terminal then uses the trip information to detect the ride-hailing trip. Specifically, it detects the cost of the ride-hailing trip based on the cost information in the trip information, obtains a cost detection result, detects the route of the ride-hailing trip based on the route information, obtains a route detection result, and detects the duration of the ride-hailing trip based on the duration information, obtains a duration detection result. Based on the cost detection result, route detection result, and duration detection result, the detection result of the ride-hailing trip is determined.

[0098] Specifically, when at least one of the fare detection result, route detection result, and duration detection result indicates an anomaly in the ride-hailing trip, a detection result indicating an anomaly in the fare of the ride-hailing trip is determined. Here, an anomaly in the fare detection result could be, for example, that the passenger is charged before boarding, or that the fare exceeds the expected fare significantly. An anomaly in the route detection result could be, for example, that the trip route is different from the expected route, or that the distance of the route exceeds the expected distance significantly. An anomaly in the duration detection result could be, for example, that the duration exceeds the expected duration significantly. This application does not limit the scope of the anomaly.

[0099] It should be noted that the detection process can also be implemented on the server side. Specifically, after the ride-hailing trip ends, the terminal sends a trip detection request to the server. Based on this request, the server obtains the trip information, performs detection on the ride-hailing trip based on the information, obtains the detection result, and then sends the detection result to the terminal. This application does not limit the scope of this embodiment.

[0100] In practice, after the countdown is displayed on the payment confirmation screen, a payment success screen can also be displayed when the countdown ends and no trigger operation for the appeal entry is received; the payment success screen is used to indicate that the fare for the ride-hailing trip has been paid.

[0101] It should be noted that since an automatic payment method has been set up, if no trigger action is received for the appeal portal before the countdown ends, the fare for the ride-hailing trip will be automatically deducted, thus switching from the payment confirmation screen to the payment success screen.

[0102] For example, see Figure 6 , Figure 6 This is a schematic diagram of the payment success interface provided in the embodiments of this application, based on Figure 6 In response to ending the ride-hailing trip, the following message will be displayed: Figure 6 The payment confirmation interface shown in image 'a' will automatically deduct the fare for the ride-hailing trip when the countdown ends and no trigger action is received for the appeal portal. Figure 6 The payment confirmation interface shown in Figure 'a' has switched to displaying the following: Figure 6 The payment success screen shown in b.

[0103] It should be noted that if no trigger operation is received for the appeal entry when the countdown ends, the appeal entry can still be displayed on the payment success interface after switching from the payment confirmation interface to the payment success interface. That is, the appeal entry is displayed on the payment success interface when the ride-hailing trip has been paid. The process of displaying the appeal entry on the payment success interface when the ride-hailing trip has been paid will be described below, and will not be repeated in this application embodiment.

[0104] In other embodiments, when the appeal entry is displayed on the payment success screen when the ride-hailing trip has been paid, the process of displaying the appeal entry for the ride-hailing trip in response to the end of the ride-hailing trip may be as follows: in response to the end of the ride-hailing trip and the fare for the ride-hailing trip has been paid, a payment success screen is displayed; wherein, the payment success screen is used to indicate that the fare for the ride-hailing trip has been paid; and the appeal entry for the ride-hailing trip is displayed on the payment success screen.

[0105] It should be noted that the payment success screen for the ride-hailing trip can be displayed after automatic payment or after the passenger manually pays for the ride-hailing trip. This embodiment of the application does not limit this. For example, see... Figure 7 , Figure 7 This is a schematic diagram showing the appeal entry point provided in this application embodiment displayed on the payment success screen, based on... Figure 7 The dashed box 701 indicates the appeal portal.

[0106] Step 102: In response to the trigger operation for the appeal entry, the appeal confirmation interface is displayed. The appeal confirmation interface is used to confirm the cost of the ride-hailing trip. The appeal confirmation interface includes a negation control, which is used to indicate the rejection of the cost of the ride-hailing trip.

[0107] In practice, as mentioned above, the appeal entry point can be a control or a text link. Therefore, when a trigger operation is received targeting the appeal entry point, an appeal confirmation interface including a negation control will also be displayed. This interface includes both a negation control and a confirmation control to confirm the fare for the ride-hailing trip. Specifically, the appeal confirmation interface displays a confirmation control to confirm the fare for the ride-hailing trip. When the fare for the ride-hailing trip has been paid, a payment success interface is displayed in response to the trigger operation targeting the confirmation control. This payment success interface indicates that the fare for the ride-hailing trip has been paid. When the fare for the ride-hailing trip has not been paid and the payment method is manual, a payment confirmation interface is displayed in response to the trigger operation targeting the confirmation control. This payment confirmation interface is used to pay the fare for the ride-hailing trip. When the fare for the ride-hailing trip has not been paid and the payment method is automatic, a payment success interface is displayed in response to the trigger operation targeting the confirmation control.

[0108] It should be noted that if the fare for the ride-hailing trip has not yet been paid and the payment method is automatic payment, the fare will be deducted and a payment success screen will be displayed when a confirmation action is received. If the fare for the ride-hailing trip has not yet been paid and the payment method is automatic payment, the system will switch from the appeal confirmation screen to the payment confirmation screen when a confirmation action is received, and the fare will be paid based on the payment confirmation screen. If the fare for the ride-hailing trip has already been paid, the payment success screen will be displayed directly when a confirmation action is received.

[0109] For example, see Figure 8 , Figure 8 This is a schematic diagram of the appeal determination interface provided in the embodiments of this application, based on Figure 8 801 indicates a negative control, and 802 indicates a confirm control, thus responding to a trigger action on the appeal entry and displaying, as shown below. Figure 8 The appeal confirmation interface, as indicated, includes a denial control as indicated in 801 and a confirmation control as indicated in 802.

[0110] Step 103: In response to the triggering operation of the negative control, when the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed; wherein, the fare waiver information is used to indicate that at least part of the fare for the ride-hailing trip has been waived.

[0111] It should be noted that "at least part of the fee has been waived" can mean either a full waiver or a partial waiver; this application does not limit this. The first fee waiver adjustment includes a first waiver condition and a second waiver adjustment. When a ride-hailing trip meets either the first waiver condition or the second waiver adjustment, it can be determined that the ride-hailing trip meets the first fee waiver adjustment. Both the first and second waiver conditions indicate that the cause of the abnormal ride-hailing trip fee is related to the driver. The first waiver condition indicates that the probability that the cause of the abnormal ride-hailing trip fee is related to the driver reaches a first target probability, such as 100%, meaning that the responsibility for the abnormal ride-hailing trip fee lies with the driver. The second waiver condition indicates that the probability that the cause of the abnormal ride-hailing trip fee is related to the driver is less than the first target probability but greater than the second target probability. The first target probability is greater than the second target probability, meaning that the responsibility for the abnormal ride-hailing trip fee is highly likely to lie with the driver.

[0112] In actual implementation, in response to the triggering operation of the negative control, the process of displaying the fee waiver information when the ride-hailing trip meets the first fee waiver condition can be as follows: in response to the triggering operation of the negative control, the ride-hailing trip is detected and a detection result is obtained; wherein, the detection result is used to indicate whether the ride-hailing trip meets the first fee waiver condition; when the detection result indicates that the ride-hailing trip meets the first fee waiver condition, the fee waiver information is displayed.

[0113] The process of detecting ride-hailing trips and obtaining detection results involves, specifically, acquiring trip information, driver information, and passenger information for the ride-hailing trip, and then detecting the ride-hailing trip based on this information to obtain the detection results. Here, the trip information is as described above and will not be repeated here. Driver information can include other passengers' evaluations of the driver, the driver's years of driving experience, positive review rate, complaint rate, etc., while passenger information can include other drivers' evaluations of passengers, passenger complaint rate, passenger account level, etc.

[0114] It should be noted that the trip information, driver information, and passenger information can be obtained from the server side. For example, after receiving a trigger operation for the negative control, the terminal sends an information retrieval request to the server, so that the server, based on the information retrieval request, sends the trip information, driver information, and passenger information of the ride-hailing trip to the terminal. The terminal then uses this information to detect the ride-hailing trip. Correspondingly, the detection process can also be implemented on the server side. Specifically, after receiving a trigger operation for the negative control, the terminal sends a trip detection request to the server, so the server, based on this request, obtains the trip information, driver information, and passenger information of the ride-hailing trip, and uses this information to detect the ride-hailing trip, obtaining the detection result, and then sending the detection result to the terminal. This application does not limit this aspect.

[0115] In practice, as mentioned earlier, the ride-hailing trip was previously checked based on the trip information, and the results of that check indicated whether any anomalies had occurred. Here, the results indicate whether the trip meets the first waiver condition, i.e., whether a waiver should be granted. If the results indicate that the trip meets the first waiver condition, a waiver is deemed appropriate. If the results indicate that the trip meets the second waiver condition, a waiver is deemed highly probable. Thus, by performing a second check on the ride-hailing trip based on trip information, driver information, and passenger information, the accuracy of the waiver is determined, enriching the information dimensions required for the check process and improving the accuracy of the results, thereby enhancing the accuracy of the waiver process.

[0116] Next, we will explain the process of displaying fee waiver information when the ride-hailing trip meets the first or second waiver condition, respectively, in response to the triggering operation of the negative control.

[0117] In some embodiments, when a ride-hailing trip meets the first exemption condition, in response to a triggering operation on a negative control, the process of displaying fee exemption information when the ride-hailing trip meets the first fee exemption condition may be as follows: in response to a triggering operation on a negative control, when the ride-hailing trip meets the first exemption condition and the fare for the ride-hailing trip has not yet been paid, the first fee exemption information is displayed; wherein, the first fee exemption information is used to indicate that at least part of the fare for the ride-hailing trip has been exempted.

[0118] It should be noted that when the fare for a ride-hailing trip has not yet been paid, the first fee waiver information means that the fare for the ride-hailing trip does not need to be paid, that is, the fare for the ride-hailing trip is directly waived. For example, it could be "After verification, the order fee has been waived".

[0119] For example, see Figure 9 , Figure 9 This is a schematic diagram of the first fee waiver information provided in the embodiments of this application, based on Figure 9 The dashed box 901 indicates the first fee waiver information. When the ride-hailing trip meets the first waiver conditions and the fare for the ride-hailing trip has not yet been paid, the first fee waiver information as indicated by the dashed box 901 is displayed.

[0120] In practice, the fare for a ride-hailing trip may have already been paid, such as through automatic payment or manual payment by the passenger. Therefore, in response to a triggering operation on a negative control, the process of displaying fare waiver information when the ride-hailing trip meets the first fare waiver condition can be as follows: in response to a triggering operation on a negative control, when the ride-hailing trip meets the first waiver condition and the fare for the ride-hailing trip has already been paid, second fare waiver information is displayed; wherein, the second fare waiver information is used to indicate that at least a portion of the fare for the ride-hailing trip has been refunded.

[0121] It should be noted that once the fare for a ride-hailing trip has been paid, the fare needs to be refunded. In other words, the second fee waiver information refers to the fact that the fare for the ride-hailing trip needs to be refunded. For example, it could be "After verification, the order fee has been refunded".

[0122] For example, see Figure 10 , Figure 10 This is a schematic diagram of the second fee waiver information provided in the embodiments of this application, based on Figure 10 The dashed box 1001 indicates the second fee waiver information. When the ride-hailing trip meets the first waiver condition and the fare for the ride-hailing trip has been paid, the second fee waiver information as indicated by the dashed box 1001 is displayed.

[0123] In this way, by detecting ride-hailing trips in advance, when it is determined that the ride-hailing trip meets the first exemption condition, that is, the driver should bear full responsibility, at least part of the ride-hailing trip fee can be directly exempted, which improves the efficiency of ride-hailing trip processing, and also improves the efficiency of handling passenger complaints.

[0124] In other embodiments, when a ride-hailing trip meets the second exemption condition, in response to a triggering operation on a negation control, the process of displaying exemption information when the ride-hailing trip meets the first exemption condition may be as follows: in response to a triggering operation on a negation control, when the ride-hailing trip meets the second exemption condition, a negation reason submission interface is displayed; wherein, the negation reason submission interface is used to input and submit the reason for negating the ride-hailing trip's fee; in response to the negation reason submitted based on the negation reason submission interface, third exemption information is displayed; wherein, the third exemption information is used to indicate that at least a portion of the ride-hailing trip's fee is temporarily exempted.

[0125] It should be noted that, as mentioned above, the second exemption condition refers to the fact that the responsibility for the abnormal fare of the ride-hailing trip is most likely to lie with the driver. In other words, the responsibility for the abnormal fare of the ride-hailing trip may also be unrelated to the driver. Therefore, when a trigger operation is received for the negative control, the fare of the ride-hailing trip cannot be directly exempted as if the ride-hailing trip meets the first exemption condition. Instead, a negative reason submission interface needs to be displayed. Based on the negative reason submission interface, the detailed reason for the passenger's rejection of the ride-hailing fare can be obtained, and then it can be determined whether to exempt at least part of the fare of the ride-hailing trip.

[0126] It should be noted that the process of displaying the third fee waiver information in response to the negative reason submitted on the negative reason submission interface can be a response to a confirmation instruction for the negative reason submitted on the negative reason submission interface. For example, displaying a submission control on the negative reason submission interface, thereby receiving a confirmation instruction in response to the triggering operation of the submission control, that is, the negative reason submitted on the negative reason submission interface.

[0127] Temporarily waiving at least a portion of the fare for a ride-hailing trip refers to the process of obtaining detailed reasons for a passenger's denial of the fare from the negative reason submission interface, detecting whether to waive at least a portion of the fare, and then waiving at least a portion of the fare. Once the detection result is determined, it is then determined whether the passenger needs to pay at least a portion of the fare again, or whether to completely waive at least a portion of the fare. "Temporarily" refers to a target duration, which is related to the process of obtaining detailed reasons for a passenger's denial of the fare from the negative reason submission interface and detecting the fare. For example, it could be one or two days, which is not limited by the embodiments of this application.

[0128] For example, see Figure 11 , Figure 11 This is a schematic diagram of the third fee exemption information provided in the embodiments of this application, based on Figure 11 The dashed box 1101 indicates the third fee waiver information. When the ride-hailing trip meets the second waiver conditions, the third fee waiver information as indicated by the dashed box 1101 is displayed.

[0129] It should be noted that when a ride-hailing trip meets the second exemption condition, if the fare for the ride-hailing trip has already been paid, the third exemption information refers to a temporary refund of at least a portion of the fare for the ride-hailing trip; if the fare for the ride-hailing trip has not been paid, the third exemption information refers to a temporary exemption of at least a portion of the fare for the ride-hailing trip.

[0130] In actual implementation, after displaying the negative reason submission interface, it is also possible to: respond to input operations on the negative reason submission interface; display the entered negative reason on the negative reason submission interface; display a submission control for submitting the negative reason entered on the negative reason submission interface; and receive the negative reason submitted on the negative reason submission interface in response to a trigger operation on the submission control.

[0131] It should be noted that on the reason for rejection submission interface, the reason for rejection can be provided with multiple options for passengers to choose from, or it can be provided with a text input box for passengers to input. This application embodiment does not limit this.

[0132] For example, see Figure 12 , Figure 12 This is a schematic diagram of the negative reason submission interface provided in an embodiment of this application, based on Figure 12 In such Figure 12 The submission interface for negative reasons, as shown, displays the entered negative reason, and, for example... Figure 12 The submit control indicated by 1201, in response to the triggering operation on the submit control, receives the negative reason submitted by the negative reason submission interface.

[0133] It should be noted that after receiving the negative reason submitted based on the negative reason submission interface in response to the trigger operation of the submission control, a submission success message can also be displayed. The submission success message is used to indicate that the negative reason was submitted successfully, and the ride-hailing trip will be detected based on the negative reason. Then, a confirmation control is displayed, and based on the submission success message, in response to the trigger operation of the confirmation control, the third fee waiver information is displayed.

[0134] For example, see Figure 13 , Figure 13 This is a schematic diagram of the submission success message provided in an embodiment of this application, based on... Figure 13 In response to a trigger action on the submit control, after receiving a negative reason submitted from the negative reason submission interface, the following is displayed: Figure 13 The submission success message indicated by the dashed box 1301 in section a and the confirmation control indicated by 1302, thereby, based on the submission success message, in response to a triggering operation on the confirmation control, display as shown in section a. Figure 13 The third fee waiver information is indicated by the dashed box 1303 in b.

[0135] In practice, after displaying the third fee waiver information, explanatory information may also be displayed in response to the triggering operation of the third fee waiver information; wherein, the explanatory information is used to explain the process of temporarily waiving at least part of the cost of the ride-hailing trip indicated by the third fee waiver information.

[0136] It should be noted that the explanatory information is used to explain the process of temporarily waiving at least a portion of the fare for a ride-hailing trip as indicated in the third-party fare waiver information; that is, to explain how to temporarily waive at least a portion of the fare for a ride-hailing trip. For example, see [link to relevant documentation]. Figure 14 , Figure 14 This is a schematic diagram illustrating the explanatory information provided in the embodiments of this application, based on... Figure 14 In response to such Figure 14 The triggering operation for the third fee waiver information indicated by the dashed box 1401 in section a is displayed as follows: Figure 14 The explanatory information indicated in section b, 1402, states that the ride-hailing service will temporarily exempt passengers from paying the fare for the ride-hailing trip until the fare processing is completed for a negative reason. Once the fare processing is completed, if the trip is confirmed to be abnormal, at least a portion of the fare will be waived for the passenger. If the trip is confirmed to be normal, the passenger will still need to pay the fare for the ride-hailing trip.

[0137] In practice, after displaying the negative reason submission interface, a processing prompt message can also be displayed in response to the negative reason submitted based on the negative reason submission interface; the processing prompt message is used to indicate the processing status of the ride-hailing trip fee.

[0138] It should be noted that the processing notification message indicates that the fare for the ride-hailing trip is being processed based on a negative reason; for example, see [link to example]. Figure 15 , Figure 15 This is a schematic diagram of the processing prompt information provided in the embodiments of this application, based on Figure 15 In response to a negative reason submitted through the negative reason submission interface, the following is displayed: Figure 15 The processing prompt information indicated by 1501.

[0139] In some embodiments, when the fee waiver information includes third fee waiver information for indicating a temporary waiver of at least part of the fare for a ride-hailing trip, after displaying the fee waiver information, the ride-hailing trip creation interface may also be displayed in response to the display operation of the ride-hailing trip creation interface; and in response to the trip creation operation triggered based on the creation interface, if the fare for the ride-hailing trip has not yet been paid, a new ride-hailing trip may be created.

[0140] It should be noted that, generally, if the fare for the previous ride-hailing trip is unpaid, a new ride-hailing trip cannot be created. However, here, during the process of displaying the third fare waiver information—that is, during the re-examination of the ride-hailing trip fare based on negative reasons—even if the fare for the ride-hailing trip has not been paid, a new ride-hailing trip can still be created because at least a portion of the fare has been temporarily waived. Therefore, the passenger's ability to take another ride will not be affected by the ongoing re-examination of the ride-hailing trip fare based on negative reasons.

[0141] It should be noted that the detection process described above is based on trip information, passenger information, and driver information. However, this process of re-detecting the fare of a ride-hailing trip based on a negative reason is different. Even if it cannot be determined with 100% certainty that the abnormality of the ride-hailing trip is due to the driver, that is, only that the abnormality of the ride-hailing trip is highly likely to be due to the driver, the fare of the ride-hailing trip is re-detected based on the specific negative reason entered by the passenger, thereby improving the accuracy of the liability determination.

[0142] In practice, the process of re-examining the fare of a ride-hailing trip based on a negative reason can be divided into two scenarios: either the fare is determined to be normal based on the negative reason, meaning no waiver of at least part of the fare is necessary; or the fare is determined to be abnormal based on the negative reason, meaning a waiver of at least part of the fare is required. The following sections will explain these two scenarios separately.

[0143] In some embodiments, after displaying the fee waiver information, when the ride-hailing trip does not meet the second fee waiver conditions, a first prompt information may be displayed, and the display of the third fee waiver information may be switched to the display of payment success information; wherein, the first prompt information is used to indicate that the ride-hailing trip does not meet the second fee waiver conditions and that the fare for the ride-hailing trip needs to be paid, and the payment success information is used to indicate that the fare for the ride-hailing trip has been paid.

[0144] It should be noted that the second waiver condition refers to whether the fare for the ride-hailing trip should be waived based on a negative reason. The ride-hailing trip not meeting the second waiver condition means that the fare for the ride-hailing trip is determined to be normal based on a negative reason, that is, the fare for the ride-hailing trip should not be waived. Therefore, when the ride-hailing trip does not meet the second waiver condition, a first prompt message is displayed to indicate that the ride-hailing trip does not meet the second waiver condition and that the fare for the ride-hailing trip needs to be paid.

[0145] In this context, the ride-hailing trip does not meet the second fare waiver condition; that is, the ride-hailing trip meets the first fare waiver condition but does not meet the second fare waiver condition. Regarding the process of switching the display of the third fare waiver information to the display of payment success information, when the payment method for the ride-hailing trip is automatic payment, the fare is automatically deducted, thus directly switching the display of the third fare waiver information to the display of payment success information. When the fare for the ride-hailing trip is manually paid, the interface displaying the third fare waiver information switches to the payment confirmation interface, thus responding to the payment operation performed based on the payment confirmation interface and displaying payment success information.

[0146] For example, see Figure 16 , Figure 16 This is a schematic diagram illustrating the process when a ride-hailing trip does not meet the second fare waiver condition, based on an embodiment of this application. Figure 16 When a ride-hailing trip does not meet the conditions for the second fare waiver, the following will be displayed: Figure 16 The third fee waiver information indicated by the dashed box 1601 in section a is switched to display as follows: Figure 16 The payment success information indicated by the dashed box 1602 in b.

[0147] In other embodiments, after displaying the fee waiver information, in response to a triggering operation on a negative control, when the ride-hailing trip meets the second fee waiver condition, a second prompt message is displayed, and the display of the third fee waiver information is switched to the display of the target fee waiver information; wherein, the second prompt message is used to indicate that the ride-hailing trip meets the second fee waiver condition and that at least part of the ride-hailing trip fee does not need to be paid, and the target fee waiver information is used to indicate that at least part of the ride-hailing trip fee has been waived.

[0148] It should be noted that, as mentioned above, the second fee waiver condition refers to whether the fare for a ride-hailing trip should be waived based on a negative reason. Meeting the second fee waiver condition for a ride-hailing trip means that the fare for the ride-hailing trip is determined to be abnormal based on a negative reason, that is, the fare for the ride-hailing trip should be waived. Therefore, when the ride-hailing trip meets the second fee waiver condition, a second prompt message is displayed to indicate that the ride-hailing trip meets the second fee waiver condition and that the fare for the ride-hailing trip does not need to be paid.

[0149] Here, the ride-hailing trip meets the second fare exemption condition, that is, the ride-hailing trip meets both the first and second fare exemption conditions. As for the process of switching from displaying the third fare exemption information to displaying the first fare exemption information, the target fare exemption information is one of the first and second fare exemption information mentioned above. When the fare for the ride-hailing trip has been paid, the target fare exemption information is the second fare exemption information, and when the fare for the ride-hailing trip has not been paid, the target fare exemption information is the first fare exemption information.

[0150] For example, see Figure 17 , Figure 17 This is a schematic diagram illustrating the process when a ride-hailing trip meets the second fare exemption condition, as provided in the embodiments of this application. Figure 17 If a ride-hailing trip meets the second fare waiver condition but the fare is not paid, the following will be displayed: Figure 17 The third fee waiver information indicated by the dashed box 1701 in section a is switched to display as follows: Figure 17 The first fee waiver information is indicated by the dashed box 1702 in section b; if the fare for the ride-hailing trip has already been paid, it will be displayed as follows. Figure 17 The third fee waiver information indicated by the dashed box 1701 in section a is switched to display as follows: Figure 17 The second fee waiver information is indicated by the dashed box 1703 in c.

[0151] By applying the above embodiments of this application, at the end of a ride-hailing trip, an appeal portal for the trip is directly displayed. Upon receiving a trigger operation for the appeal portal, an appeal confirmation interface is displayed. Responding to the trigger operation of the negation control on the appeal confirmation interface, if the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed. Thus, if a passenger disagrees with the fare for a ride-hailing trip, they can directly appeal the fare based on the trigger operation of the negation control on the appeal confirmation interface. Compared to the cumbersome complaint process for ride-hailing trip fares in related technologies, this improves the efficiency of handling ride-hailing trips.

[0152] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0153] In related technologies, if passengers complain about the cost of ride-hailing trips, the following problems exist: First, most complaints rely on expert experience and manually defined rules. This approach lacks universality, consumes a lot of manpower, is inefficient, and has poor accuracy. Moreover, due to the numerous and interrelated factors affecting liability determination, manual rules are difficult to refine. Second, it does not fully consider all types of order data and fails to adequately consider the spatiotemporal attributes of the data, resulting in less than ideal liability assessment. Third, most liability assessments are conducted after the fact, lacking the ability to identify and resolve problems in advance.

[0154] Based on this, this application provides a solution for determining liability between drivers and passengers in ride-hailing services that charge for non-ride rides. It uses historical data for standardized processing, generates data through preliminary feature extraction, and then uses a model for liability determination without human intervention. Furthermore, it employs a dual XGBoost model algorithm for liability determination and uses Bayesian optimization for parameter space exploration. It also subdivides the scenario to the non-ride ride charging scenario, and the liability determination is performed after the order is generated but before the user files a complaint, thus improving the accuracy of liability determination and user experience.

[0155] Next, the technical solution of this application will be described from the product perspective. (See [link]) Figure 18 , Figure 18 This is a flowchart of the ride-hailing driver and passenger liability determination scheme for non-ride riders provided in this application embodiment, based on... Figure 18 According to steps 1801 to 1807, the algorithm maps different probabilities of liability to four liability outcomes for the "no-ride fare deduction" problem: definitely (driver) liable, highly likely liable, definitely not liable, and indeterminate. Without a liability assessment process, the deduction process will begin after the ride ends and the bill is generated. If the payment method for this order is automatic deduction without a password, the deduction will usually be made immediately. With the liability assessment process in place, the product flow, including the payment process, will be adjusted based on these four different liability outcomes to improve the user experience.

[0156] In actual implementation, see Figure 19 , Figure 19 This is a schematic diagram illustrating the process of determining driver liability provided in an embodiment of this application, based on... Figure 19 If it is determined that "the driver is definitely at fault", such as Figure 19As shown in sections a to d, the original automatic deduction time is first extended to allow a few minutes for the user to confirm whether they accept the bill. If the user does not accept the bill or complains about the "deduction for not taking the ride" issue through any channel, the bill's direct fare adjustment process is triggered, and the accountability process ends. Compared to the "order deducted first – user discovers problem and complains – waits for customer service to process the ticket" process in related technologies, this process can resolve user issues immediately. It avoids the one or two days that customer service typically takes to process tickets manually, where timeliness cannot be guaranteed, and problems may not be effectively resolved due to poor communication between customer service and users. If the user accepts the bill or confirms payment in advance, the deduction process is triggered, and the accountability process ends.

[0157] It should be noted that, as Figure 19 As shown in sections e to h, if a user "does not confirm within the time limit," a deduction process will still be triggered to avoid unnecessary bad debts. However, the user will be given additional time to confirm the bill. If the user "does not accept the bill" or complains about the "deduction for not taking the ride" issue through any channel within this timeframe, a direct refund process will be triggered, and the liability assessment process will end. If the user "accepts the bill," the liability assessment process will end.

[0158] In actual implementation, see Figure 20 , Figure 20 This is a schematic diagram illustrating the process where the driver is likely at fault, as provided in the embodiments of this application. Figure 20 If the system determines that "the driver is highly likely to be at fault," it means that the algorithm alone cannot definitively determine who is responsible for the trip's problems. However, there is still a significant probability that the trip has issues. To improve user experience, the automatic deduction time will be extended, allowing users to confirm the bill within the specified time. If the user "does not accept the fee," they will be guided to submit a support ticket. A successful complaint will temporarily waive the order fee. If the user "accepts the fee" or "does not confirm within the time limit," the deduction will be triggered, and the liability determination will end.

[0159] The specific logic behind "temporarily waiving order fees" includes: 1) canceling automatic deductions for password-free payments, so users are not required to pay the fee until the work order is processed; 2) users can continue to place orders for ride-hailing services without being blocked by risk control due to pending payments. Work orders will be handled manually by customer service. After processing, the responsible party and whether the user needs to pay will be determined based on the outcome of the work order. This process also significantly improves the user experience.

[0160] In practice, if the judgment is "definitely no liability" or "cannot be determined", the procedure is the same as for cases with no liability, and the fee is deducted normally.

[0161] Next, the technical solution of this application will be described from a technical perspective. (See also...) Figure 21 , Figure 21 This is the first technical architecture diagram of the ride-hailing driver and passenger liability determination scheme for non-ride ridership provided in this application embodiment, based on... Figure 21 First, after a passenger completes a ride, the driver sends the order, and a service bill is generated on the user's side. Before the user sees the bill, a penalty for not taking the ride is determined. Second, in determining penalty for not taking the ride, real-time data is first collected and preprocessed, and offline profile features are combined. Then, Model 1 (the model for determining whether there is a penalty for not taking the ride) is called to determine if there is a penalty for not taking the ride. Third, for cases where Model 1 outputs a problem, a second judgment is made by calling Model 2 (the model for determining whether the order should be refunded). If a refund is determined to be necessary, it is issued directly after the user objects to the bill. For cases where a refund is highly likely, a work order is created and a risk control exemption is granted after the user objects to the bill.

[0162] In actual implementation, see Figure 22 , Figure 22 This is a second technical architecture diagram of the ride-hailing driver and passenger liability determination scheme for non-ride-hailing fees provided in this application embodiment, based on... Figure 22 The technical solution of this application is implemented through the following six modules: data collection module, image processing module, feature processing module, sample generation module, training module, and prediction service module. The following sections will describe each module in detail.

[0163] The data collection module is responsible for collecting real-time order data, passenger behavior data, and driver behavior data from the ride-hailing platform. This includes real-time characteristics of the current order such as actual trip duration, actual trip distance, actual amount, estimated trip duration, estimated trip distance, estimated amount, and the passenger's distance from the origin at the start and end of the order, as well as the passenger's distance from the origin at the end of the order, denoted as the first feature. This module needs to interface with the ride-hailing platform's database to ensure the real-time nature and accuracy of the data.

[0164] For the user profile processing module, the average price per ride, the number of complaints, and the status of valid complaints are constructed by integrating the user's ride-hailing data on the platform over the past six months. The driver profile includes the number of complaints against the driver on the platform over the past six months and the status of valid complaints, as well as the platform service provided by the driver, which serve as the second feature of the user and the driver.

[0165] The feature processing module is responsible for preprocessing the collected data, including cleaning, deduplication, and missing value imputation, and then assembling corresponding profile data based on the user and driver identifiers in the order. This module needs to detect and handle outliers, as well as properly impute missing values ​​to ensure the smooth progress of subsequent feature engineering and model training. It also filters out some orders that are inherently controversial, as well as orders that were canceled by either the passenger or the driver.

[0166] The sample generation module is responsible for sampling data and generating training samples based on the data, such as sampling data from the past 30 days to generate training samples.

[0167] For the training module, two models will be trained: Model 1, used to determine if an order has any issues with charges for rides not taken; and Model 2, used to determine if the order should be refunded. Specifically, the evaluation of the current order is conducted in two stages. In the first stage, a more complex XGBoost model is used to improve the model's accuracy, preventing orders without issues from being processed at this step. For orders that do have issues, and regarding whether to refund, a single-tree XGBoost model is used to visualize the results, improving the model's interpretability.

[0168] It should be noted that the training process for Model 1 includes the following three steps. Specifically, first, the training samples are divided into a training set and a validation set, and the loss function and evaluation metric are defined. The loss function can be expressed using the following formula:

[0169]

[0170] Where l is the cross-entropy function, and Ω is the regularization term, used to indicate the complexity of the function corresponding to Model 1, i.e., the tree. It is the predicted value, y i It is the corresponding label value, f t Indicates the function corresponding to Model 1.

[0171] The evaluation indicators can be expressed using the following formula:

[0172]

[0173] TP represents the number of orders that are already subject to non-ride fare charges and are also predicted to be subject to non-ride fare charges; TN represents the number of orders that are neither subject to non-ride fare charges nor are predicted to be subject to non-ride fare charges; FP represents the number of orders that are already subject to non-ride fare charges but are predicted to be subject to non-ride fare charges; and FN represents the number of orders that are already subject to non-ride fare charges but are predicted to be subject to non-ride fare charges.

[0174] Second, parameter optimization is performed using the Bayesian optimization algorithm. Specifically, the first step is to define the hyperparameter space of the XGBoost model, including the number of trees, learning rate, maximum tree depth, subsample rate, feature selection rate, and complexity control coefficient. The second step is to define the objective function f(x). This objective function is the evaluation function of the XGBoost model to be optimized. The third step is to define the optimization process, following the rules defined by the Bayesian optimizer. The fourth step is to output the optimal parameters and the optimal objective function values.

[0175] Third, reproduce the model based on the optimal parameters output after parameter optimization.

[0176] The training process for Model 2 includes the following two steps. Specifically, first, the training process for Model 2 is roughly similar to that for Model 1, with the only difference being the definition of the sample data and labels. This will not be elaborated further. Second, Model 2 trains a fixed tree and uses the Bayesian optimization algorithm to find the optimization of other parameters under the condition of a single tree.

[0177] For the prediction service module, there are two types of prediction services, with one corresponding to each model. Model 1 directly outputs whether the predicted classification value is problematic or not, while Model 2 outputs the predicted probability value, which is then divided into categories: confirmed liability, high probability of liability, indeterminate, and confirmed no liability.

[0178] Thus, the technical solution of this application improves the accuracy of determining liability when deducting fares for ride-hailing services for non-ride riders, thereby optimizing user experience and minimizing users' financial losses.

[0179] In some embodiments, the model of this application is not limited to the xgboost model, and a neural network structure can also be used to replace the current model; in addition, other methods such as random search can be selected to optimize the parameters; at the same time, this application can also use different features or add features to solve the same problem, such as other features of the current order, such as the user's voice data recorded during the trip; in addition, it can not only target the problem of charging for non-rides, but can also be extended to other problems, such as drivers taking detours.

[0180] By applying the above embodiments of this application, at the end of a ride-hailing trip, an appeal portal for the trip is directly displayed. Upon receiving a trigger operation for the appeal portal, an appeal confirmation interface is displayed. Responding to the trigger operation of the negation control on the appeal confirmation interface, if the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed. Thus, if a passenger disagrees with the fare for a ride-hailing trip, they can directly appeal the fare based on the trigger operation of the negation control on the appeal confirmation interface. Compared to the cumbersome complaint process for ride-hailing trip fares in related technologies, this improves the efficiency of handling ride-hailing trips.

[0181] The following description continues to illustrate the exemplary structure of the ride-hailing trip processing device 455 provided in the embodiments of this application as a software module. In some embodiments, such as... Figure 2 As shown, the software modules stored in the ride-hailing trip processing device 455 in the memory 450 may include:

[0182] The first display module 4551 is used to display an appeal portal for the ride-hailing trip in response to the termination of the ride-hailing trip;

[0183] The second display module 4552 is used to display an appeal confirmation interface in response to a trigger operation on the appeal entry point. The appeal confirmation interface is used to confirm the fare of the ride-hailing trip. The appeal confirmation interface includes a negation control, which is used to indicate the negation of the fare of the ride-hailing trip.

[0184] The third display module 4553 is used to respond to the triggering operation of the negative control and display fee exemption information when the ride-hailing trip meets the first fee exemption condition; wherein the fee exemption information is used to indicate that at least part of the fee for the ride-hailing trip has been exempted.

[0185] In some embodiments, the first display module 4551 is further configured to display a payment confirmation interface in response to the termination of a ride-hailing trip. The payment confirmation interface is used to instruct the user to confirm and pay the fare for the ride-hailing trip. The payment confirmation interface displays an appeal entry for the ride-hailing trip.

[0186] In some embodiments, the payment method for the ride-hailing trip is automatic payment, the appeal entry is displayed on the payment confirmation interface, and the device further includes a fourth display module, which is used to display a countdown on the payment confirmation interface; wherein the countdown is used to indicate the remaining time for payment of the ride-hailing trip fee; the first display module 4551 is also used to display the appeal confirmation interface in response to a trigger operation on the appeal entry when the countdown has not ended.

[0187] In some embodiments, the device further includes a fifth display module, which is configured to display a payment success interface when the countdown ends and no trigger operation is received for the appeal entry; wherein the payment success interface is used to indicate that the fare for the ride-hailing trip has been paid.

[0188] In some embodiments, the device further includes an acquisition module for acquiring trip information of the ride-hailing trip; the fourth display module is further configured to display the countdown on the payment confirmation interface when the trip information indicates that the cost of the ride-hailing trip is abnormal.

[0189] In some embodiments, the first display module 4551 is further configured to display a payment success interface in response to the termination of a ride-hailing trip and the payment of the ride-hailing trip; wherein the payment success interface is used to indicate that the payment of the ride-hailing trip has been made; and the payment success interface displays an appeal entry for the ride-hailing trip.

[0190] In some embodiments, the third display module 4553 is further configured to detect the ride-hailing trip in response to a trigger operation on the negative control and obtain a detection result; wherein the detection result is used to indicate whether the ride-hailing trip meets the first fare exemption condition; when the detection result indicates that the ride-hailing trip meets the first fare exemption condition, fare exemption information is displayed.

[0191] In some embodiments, the first fee waiver condition includes a first waiver condition, which indicates that the reason for the abnormality in the fare of the ride-hailing trip is related to the driver of the ride-hailing trip; the third display module 4553 is further configured to, in response to a trigger operation on the negative control, display first fee waiver information when the ride-hailing trip meets the first waiver condition and the fare of the ride-hailing trip has not yet been paid; wherein, the first fee waiver information indicates that at least a portion of the fare of the ride-hailing trip has been waived.

[0192] In some embodiments, the first fee waiver condition includes a first waiver condition, which indicates that the reason for the abnormality in the fare of the ride-hailing trip is the driver of the ride-hailing trip; the third display module 4553 is further configured to, in response to a trigger operation on the negative control, display second fee waiver information when the ride-hailing trip meets the first waiver condition and the fare of the ride-hailing trip has been paid; wherein the second fee waiver information indicates that at least a portion of the fare of the ride-hailing trip has been refunded.

[0193] In some embodiments, the first fee waiver condition includes a second waiver condition, which indicates that the reason for the abnormality in the fare of the ride-hailing trip is related to the driver of the ride-hailing trip; the third display module 4553 is further configured to, in response to a triggering operation of the negation control, display a negation reason submission interface when the ride-hailing trip meets the second waiver condition; wherein the negation reason submission interface is used to input and submit a reason for negating the fare of the ride-hailing trip; in response to the negation reason submitted based on the negation reason submission interface, display third fee waiver information; wherein the third fee waiver information is used to indicate that at least a portion of the fare of the ride-hailing trip is temporarily waived.

[0194] In some embodiments, the apparatus further includes a submission module, which is configured to, in response to an input operation on the negative reason submission interface, display the input negative reason on the negative reason submission interface; display a submission control for submitting the negative reason input based on the negative reason submission interface; and, in response to a trigger operation on the submission control, receive the negative reason submitted based on the negative reason submission interface.

[0195] In some embodiments, the device further includes a sixth display module, which is configured to display explanatory information in response to a triggering operation for third fee waiver information; wherein the explanatory information is configured to explain the process of temporarily waiving at least a portion of the fare for the ride-hailing trip as indicated by the third fee waiver information.

[0196] In some embodiments, the device further includes a seventh display module, which is configured to display processing prompt information in response to a negative reason submitted based on the negative reason submission interface; wherein the processing prompt information is used to indicate the processing status of the fare for the ride-hailing trip.

[0197] In some embodiments, the device further includes an eighth display module, which is configured to display a confirmation control on the appeal confirmation interface, the confirmation control being used to determine the cost of the ride-hailing trip; and to display a payment success interface in response to a triggering operation on the confirmation control; wherein the payment success interface is used to indicate that the cost of the ride-hailing trip has been paid.

[0198] In some embodiments, the fee waiver information includes third fee waiver information, which indicates that at least a portion of the fare for the ride-hailing trip is temporarily waived; the device further includes a ninth display module, which is configured to display a ride-hailing trip creation interface in response to a display operation of the ride-hailing trip creation interface; and to create a new ride-hailing trip in response to a trip creation operation triggered based on the creation interface if the fare for the ride-hailing trip has not yet been paid.

[0199] In some embodiments, the device further includes a tenth display module, which is configured to display a first prompt message and switch the display of the third fee waiver message to the display of payment success message when the ride-hailing trip does not meet the second fee waiver conditions; wherein the first prompt message is used to indicate that the ride-hailing trip does not meet the second fee waiver conditions and that the fare for the ride-hailing trip needs to be paid, and the payment success message is used to indicate that the fare for the ride-hailing trip has been paid.

[0200] In some embodiments, the device further includes an eleventh display module, which is configured to, in response to a triggering operation on the negative control, display a second prompt message when the ride-hailing trip meets the second fare waiver condition, and switch the display of the third fare waiver information to the display of target fare waiver information; wherein the second prompt message is used to indicate that the ride-hailing trip meets the second fare waiver condition and that at least a portion of the fare for the ride-hailing trip does not need to be paid, and the target fare waiver information is used to indicate that at least a portion of the fare for the ride-hailing trip has been waived.

[0201] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the ride-hailing trip processing method described above in this application.

[0202] This application provides a computer-readable storage medium storing executable instructions. When these executable instructions are executed by a processor, they cause the processor to execute the ride-hailing trip processing method provided in this application. For example, ... Figure 3 The method for handling ride-hailing trips is shown.

[0203] In some embodiments, the computer-readable storage medium may be a read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic surface memory, optical disk, or CD-ROM, etc.; or it may be a device that includes one or any combination of the above-mentioned memories.

[0204] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0205] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborating files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0206] As an example, executable instructions can be deployed to execute on a single electronic device, or on multiple electronic devices located in one location, or on multiple electronic devices distributed across multiple locations and interconnected via a communication network.

[0207] It should be noted that, in this application embodiment, data related to ride-hailing trips, trip information, passenger information, driver information, etc. are involved. When this application embodiment is applied to specific products or technologies, the corresponding licenses or consents need to be obtained, and the collection, use and processing of related data need to comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0208] In summary, the embodiments of this application have the following beneficial effects:

[0209] (1) If a passenger does not agree with the fare of a ride-hailing trip, he / she can directly appeal the fare of the ride-hailing trip by triggering the negative control in the appeal confirmation interface. Compared with the cumbersome complaint process for the fare of ride-hailing trips in related technologies, this improves the efficiency of handling ride-hailing trips.

[0210] (2) By detecting ride-hailing trips in advance, when it is determined that the ride-hailing trip meets the first exemption condition, that is, the driver should bear full responsibility, at least part of the cost of the ride-hailing trip can be directly exempted, which improves the efficiency of ride-hailing trip processing, that is, improves the efficiency of handling passenger complaints.

[0211] (3) Based on trip information, driver information and passenger information, a second detection is carried out on the ride-hailing trip to determine whether the ride-hailing trip fee should be waived. This enriches the dimensions of information required for the detection process, improves the accuracy of the detection results, and thus improves the accuracy of fee waiver.

[0212] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method for processing ride-hailing trips, characterized in that, The method includes: In response to the termination of the ride-hailing trip, an appeal portal for the ride-hailing trip is displayed; In response to a trigger operation on the appeal entry point, an appeal confirmation interface is displayed, which is used to confirm the cost of the ride-hailing trip. The appeal confirmation interface includes a denial control, which is used to indicate whether the fare for the ride-hailing trip is denied. In response to the triggering operation of the negative control, when the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed; The fee waiver information is used to indicate that at least a portion of the fare for the ride-hailing trip has been waived.

2. The method as described in claim 1, characterized in that, The response to ending the ride-hailing trip displays an appeal portal for the trip, including: In response to the termination of the ride-hailing trip, a payment confirmation interface is displayed, which is used to instruct the user to confirm and pay the fare for the ride-hailing trip. On the payment confirmation screen, an appeal portal for the ride-hailing trip is displayed.

3. The method as described in claim 1, characterized in that, The payment method for the ride-hailing trip is automatic payment. The appeal entry is displayed on the payment confirmation interface, which is used to instruct payment for the ride-hailing trip. The method also includes: On the payment confirmation screen, a countdown timer is displayed; the countdown timer indicates the remaining time for payment of the ride-hailing trip fare. The response to the triggered operation for the appeal entry point, displaying the appeal confirmation interface, includes: When the countdown has not ended, in response to the trigger operation for the appeal entry, the appeal confirmation interface is displayed.

4. The method as described in claim 3, characterized in that, After the countdown is displayed on the payment confirmation interface, the method further includes: When the countdown ends and no trigger operation is received for the appeal entry, the payment success interface is displayed; The payment success interface indicates that the fare for the ride-hailing trip has been paid.

5. The method as described in claim 3, characterized in that, Before the countdown is displayed on the payment confirmation interface, the method further includes: Obtain the trip information of the ride-hailing trip; The countdown displayed on the payment confirmation interface includes: When the trip information indicates that the cost of the ride-hailing trip is abnormal, the countdown will be displayed on the payment confirmation interface.

6. The method as described in claim 1, characterized in that, The response to ending the ride-hailing trip displays an appeal portal for the trip, including: Upon completion of the ride-hailing trip and payment of the fare, a payment success screen is displayed. The payment success interface indicates that the fare for the ride-hailing trip has been paid. On the payment success screen, an appeal portal for the ride-hailing trip is displayed.

7. The method as described in claim 1, characterized in that, In response to a triggering operation on the negative control, when the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed, including: In response to the triggering operation of the negative control, the ride-hailing trip is detected, and the detection result is obtained; The detection result is used to indicate whether the ride-hailing trip meets the first fee exemption condition; When the detection result indicates that the ride-hailing trip meets the first waiver condition, waiver information is displayed.

8. The method as described in claim 1, characterized in that, The first fee waiver condition includes a first waiver condition, which indicates that the reason for the abnormality in the fare of the ride-hailing trip is related to the driver of the ride-hailing trip; In response to a triggering operation on the negative control, when the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed, including: In response to the triggering operation of the negation control, when the ride-hailing trip meets the first exemption condition and the fare for the ride-hailing trip has not yet been paid, the first fare exemption information is displayed; The first fee waiver information is used to indicate that at least part of the fare for the ride-hailing trip has been waived.

9. The method as described in claim 1, characterized in that, The first fee waiver condition includes a first waiver condition, which indicates that the reason for the abnormality in the fare of the ride-hailing trip is due to the driver of the ride-hailing trip; In response to a triggering operation on the negative control, when the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed, including: In response to the triggering operation of the negation control, when the ride-hailing trip meets the first exemption condition and the fare for the ride-hailing trip has been paid, the second fare exemption information is displayed; The second fee waiver information is used to indicate that at least a portion of the fare for the ride-hailing trip has been refunded.

10. The method as described in claim 1, characterized in that, The first fee waiver condition includes a second waiver condition, which indicates that the reason for the abnormality in the fare of the ride-hailing trip is related to the driver of the ride-hailing trip. In response to a triggering operation on the negative control, when the ride-hailing trip meets the first fare waiver condition, fare waiver information is displayed, including: In response to the triggering operation of the rejection control, when the ride-hailing trip meets the second exemption condition, a rejection reason submission interface is displayed; The reason for rejection submission interface is used to input and submit the reason for rejecting the fare for the ride-hailing trip; In response to the negative reason submitted based on the negative reason submission interface, third fee waiver information is displayed; The third fee waiver information is used to indicate the temporary waiver of at least a portion of the fees for the ride-hailing trip.

11. The method as described in claim 10, characterized in that, After displaying the negative reason submission interface, the method further includes: In response to an input operation on the negative reason submission interface, the input negative reason is displayed on the negative reason submission interface; Display a submission control, which is used to submit the reason for rejection entered on the reason for rejection submission interface; In response to a trigger operation on the submit control, a negative reason submitted based on the negative reason submission interface is received.

12. The method as described in claim 10, characterized in that, After displaying the third fee waiver information, the method further includes: In response to a triggered action regarding information on waiver of third-party fees, display explanatory information; The explanatory information is used to explain the process of temporarily waiving at least a portion of the cost of the ride-hailing trip as indicated by the third fee waiver information.

13. The method as described in claim 10, characterized in that, After displaying the interface for submitting the reason for rejection, the method further includes: In response to the negative reason submitted based on the negative reason submission interface, a processing prompt message is displayed; The processing prompt information is used to indicate the processing status of the fare for the ride-hailing trip.

14. The method as described in claim 1, characterized in that, After displaying the appeal confirmation interface in response to a trigger operation on the appeal entry point, the method further includes: On the appeal confirmation interface, a confirmation control is displayed, which is used to determine the cost of the ride-hailing trip; When the fare for the ride-hailing trip has been paid, in response to the triggering operation of the confirmation control, a payment success interface is displayed; The payment success interface indicates that the fare for the ride-hailing trip has been paid.

15. The method as described in claim 1, characterized in that, The fee waiver information includes third fee waiver information, which is used to indicate that at least a portion of the fare for the ride-hailing trip will be temporarily waived; After displaying the fee waiver information, the method further includes: In response to the display operation of the ride-hailing trip creation interface, the ride-hailing trip creation interface is displayed; In response to the trip creation operation triggered by the creation interface, if the fare for the ride-hailing trip has not yet been paid, a new ride-hailing trip is created.

16. The method as described in claim 15, characterized in that, After displaying the fee waiver information, the method further includes: When the ride-hailing trip does not meet the second fee waiver conditions, the first prompt message is displayed, and the display of the third fee waiver message is switched to the display of payment success message; The first prompt message is used to indicate that the ride-hailing trip does not meet the second fee exemption conditions and that the fare for the ride-hailing trip needs to be paid. The payment success message is used to indicate that the fare for the ride-hailing trip has been paid.

17. The method as described in claim 15, characterized in that, After displaying the fee waiver information, the method further includes: In response to the triggering operation of the negative control, when the ride-hailing trip meets the second fare exemption condition, a second prompt message is displayed, and the display of the third fare exemption information is switched to the display of the target fare exemption information; The second notification information is used to indicate that the ride-hailing trip meets the second fee waiver condition and that at least part of the ride-hailing trip fee does not need to be paid. The target fee waiver information is used to indicate that at least part of the ride-hailing trip fee has been waived.

18. A device for processing ride-hailing trips, characterized in that, The device includes: The first display module is used to display an appeal portal for the ride-hailing trip in response to the termination of the ride-hailing trip; The second display module is used to display an appeal confirmation interface in response to a trigger operation on the appeal entry point. The appeal confirmation interface is used to confirm the fare for the ride-hailing trip. The appeal confirmation interface includes a negation control, which is used to indicate that the fare for the ride-hailing trip is denied. The third display module is used to respond to the triggering operation of the negative control and display fee exemption information when the ride-hailing trip meets the first fee exemption condition; wherein the fee exemption information is used to indicate that at least part of the fee for the ride-hailing trip has been exempted.

19. An electronic device, characterized in that, include: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the ride-hailing trip processing method according to any one of claims 1 to 17.

20. A computer-readable storage medium, characterized in that, It stores executable instructions for causing a processor to execute, thereby implementing the ride-hailing trip processing method according to any one of claims 1 to 17.

21. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the processor, they implement the ride-hailing trip processing method according to any one of claims 1 to 17.

Images