CN110766391B

CN110766391B - Service order payment method and device, electronic equipment and storage medium

Info

Publication number: CN110766391B
Application number: CN201910153547.8A
Authority: CN
Inventors: 金丽华; 马宁; 王小雪; 史雅琦
Original assignee: Beijing Didi Infinity Technology and Development Co Ltd
Current assignee: Beijing Didi Infinity Technology and Development Co Ltd
Priority date: 2019-02-28
Filing date: 2019-02-28
Publication date: 2021-03-02
Anticipated expiration: 2039-02-28
Also published as: CN112819456A; CN110766391A

Abstract

The application provides a service order payment method, a service order payment device, electronic equipment and a storage medium, wherein the method comprises the following steps: displaying a first operation button when the service order is completed; receiving a digital object unique identifier associated with the service order sent by a server in response to operation of the first operation button by a service provider; displaying the digital object unique identifier, the digital object unique identifier identifying a payment link for the service order. According to the method and the device, when the service order is finished, the unique identifier of the digital object associated with the service order is obtained from the server for the service requester to pay for the service order, so that the effect that the payment condition of the service requester is associated with the service order and the server can conveniently obtain the payment details of the service order is achieved.

Description

Service order payment method and device, electronic equipment and storage medium

Technical Field

The application relates to the technical field of internet, in particular to a service order payment method and device, electronic equipment and a storage medium.

Background

With the development of internet and intelligent terminal technologies, various Applications (APPs) providing convenience for life are also in the endlessly, and provide services for people who eat and wear, and the users need to pay corresponding money to service providers.

Taking a network taxi taking as an example, a user uses the taxi taking APP to take a taxi, and when a taxi taking order is finished, a taxi driver needs to select a payment mode to complete the whole journey. Currently, the payment modes selectable by the taxi driver include online payment and cash payment, wherein the online payment is input by the taxi driver for the fare amount, the user pays through a payment component of the taxi-taking APP (namely, a cashier payment function called when the user takes the fare amount of the taxi-taking order on the payment line), and when the taxi driver selects the cash payment, the user is indicated to be charged with cash by himself.

Among the prior art, when the user does not carry cash and user's APP of taking a car does not bind the payment function after taking a car, need the taxi driver to select cash payment earlier and accomplish the payment link of stroke, show the two-dimensional code of oneself (the two-dimensional code of the APP first page of APP of taking a car of entity card tablet or driver terminal) to the user again, the user sweeps the sign indicating number payment through third party software, because sweep sign indicating number payment link and order separation of taking a car, the platform of taking a car can't take notes the payment details of the order of should taking a car, be unfavorable for subsequent data analysis or provide relevant maintenance service.

Disclosure of Invention

In view of this, an object of the embodiments of the present application is to provide a service order payment method, an apparatus, an electronic device, and a storage medium, which can provide a unique identifier of a digital object associated with a service order for a service requester to pay for the service order, solve the problem that a code scanning payment link is separated from a taxi-taking order in the prior art, which causes a server to be unable to learn payment details of the taxi-taking order, and achieve the effects of associating a payment condition of the service requester with the service order and facilitating the server to learn the payment details of the service order.

In a first aspect, an embodiment of the present application provides a service order payment method, where the method includes:

displaying a first operation button when the service order is completed;

receiving a digital object unique identifier associated with the service order sent by a server in response to operation of the first operation button by a service provider;

displaying the digital object unique identifier, wherein the digital object unique identifier is used to identify a payment link for the service order.

In the application, the unique identifier of the digital object sent by the server can be automatically acquired through the operation of the first operation button by the service provider, compared with a code scanning payment mode in the prior art, the operation process is simplified, the operation experience of the service provider is improved, and the waiting cost of the service requester is reduced; the digital object unique identifier is associated with the service order, and the digital object unique identifier identifies the payment link of the service order, so that the service requester can pay for the service order according to the digital object unique identifier, when the service requester pays for the service order according to the digital object unique identifier, the server can obtain the payment details of the service order, and once a payment dispute occurs subsequently, the server is well documented.

In some embodiments, the step of displaying the first operation button when the service order is completed comprises:

and responding to the confirmation operation of the service provider on the completion of the service order, and displaying the first operation button.

In some embodiments, the method further comprises:

and displaying a service ending page corresponding to the processing process according to different processing processes of the service order by the service requester based on the unique identifier of the digital object.

In the application, in the process that the service requester processes the service order according to the unique identifier of the digital object, the service provider terminal can display different service ending pages for different processing processes so as to realize automatic skipping of the process, thereby saving the operation of the service provider.

In some embodiments, the step of displaying a service end page corresponding to the processing progress according to different processing progresses of the service order by the service requester based on the digital object unique identifier comprises:

when the processing process represents that the service requester does not confirm payment amount, displaying a first service end page; the first service end page comprises a first payment state and a payment mode of the service requester.

In some embodiments, the method further comprises:

and displaying a second operation button on the first service ending page, wherein the payment mode corresponding to the first operation button is different from the payment mode corresponding to the second operation button.

In the application, when the service provider terminal displays the first service end page, it indicates that the service requester does not confirm the payment amount, which also means that the payment is not completed, and when the service requester wants to change the payment mode, the service provider can change the current payment mode from the payment mode corresponding to the first operation button to the payment mode corresponding to the second operation button by operating the second operation button displayed on the first service end page.

when the processing process represents that the service requester confirms the payment amount and does not finish the payment, displaying a second service ending page; wherein the second service end page includes a second payment status, a payment amount, and a payment method of the service requester.

In some embodiments, the method further comprises:

and displaying a second operation button on the second service ending page, wherein the payment mode corresponding to the first operation button is different from the payment mode corresponding to the second operation button.

In this application, when the service provider terminal displays the second service end page, it indicates that the service requester has confirmed the payment amount, but actually has not completed the payment, and when the service requester wants to change the payment method, the service provider may change the current payment method from the payment method corresponding to the first operation button to the payment method corresponding to the second operation button by operating the second operation button displayed on the second service end page.

displaying a third service ending page when the processing process represents that the service requester confirms the payment amount and completes the payment; wherein the third service end page includes a third payment status, a payment amount, and a payment method of the service requester.

In some embodiments, the step of displaying the first operation button when the service order is completed comprises: when the service order is completed, displaying the first operating button and the second operating button; the payment mode corresponding to the first operation button is different from the payment mode corresponding to the second operation button;

the method further comprises the following steps:

and when the service provider selects to change the payment mode corresponding to the second operation button into another payment mode, displaying the first operation button in a floating layer mode.

In this application, when the service order is finished, the service provider terminal may display a first operation button and a second operation button for the service provider to select different payment methods, and if the service provider initially selects a payment method corresponding to the second operation button, and when the service requester does not complete payment, the payment method needs to be changed, the first operation button may be displayed in a floating layer manner, so that the service provider changes the payment method corresponding to the second operation button to the payment method corresponding to the first operation button.

In some embodiments, the step of displaying the unique identifier of the digital object comprises:

displaying the digital object unique identifier in a floating layer manner.

In some embodiments, the digital object unique identifier includes an order number, an order type, time information, identification information of the service provider, and identification information of the service requester corresponding to the service order.

In the present application, the unique identifier of the digital object includes the relevant data of the service order, i.e. the order number, the order type, the time information, the identification information of the service provider and the identification information of the service requester, so that the association with the service order is realized.

In some embodiments, the digital object unique identifier is a two-dimensional code or a bar code.

In this application, the unique identifier of the digital object may be a two-dimensional code or a bar code, and the service requester may scan the unique identifier of the digital object using third-party software to pay for the service order.

In a second aspect, an embodiment of the present application provides another service order payment method, where the method includes:

generating a digital object unique identifier associated with a service order when payment means confirmation information transmitted by a service provider terminal in response to an operation of a first operation button by a service provider is received, wherein the first operation button is displayed on the service provider terminal when the service order is completed;

transmitting the digital object unique identifier to the service provider terminal, wherein the digital object unique identifier displayed on the service provider terminal is used to identify a payment link for the service order.

In the application, the service provider operates a first operation button displayed on the service provider terminal to enable the service provider terminal to send payment mode confirmation information to the server, the server generates a digital object unique identifier associated with a service order according to the payment mode confirmation information and issues the digital object unique identifier to the service provider terminal so that the service provider terminal displays the digital object unique identifier, a service requester can pay for the service order according to the digital object unique identifier displayed on the service provider terminal because the digital object unique identifier is associated with the service order and the digital object unique identifier identifies a payment link of the service order, and the server can obtain payment details of the service order after a service requester pays for the service order according to the digital object unique identifier, once payment disputes subsequently appear, the server is well documented.

In some embodiments, the step of generating a unique identifier for the digital object associated with the service order comprises:

and generating the unique identifier of the digital object according to the order number, the order type and the time information corresponding to the service order, the identification information of the service provider and the identification information of the service requester.

In the application, the server generates a digital object unique identifier according to an order number, an order type, time information, identification information of a service provider and identification information of a service requester corresponding to a service order, so that the digital object unique identifier includes data of the service order and is associated with the service order.

In some embodiments, the method further comprises:

and when receiving confirmation operation information sent by the service provider terminal in response to the confirmation operation of the service provider for the completion of the service order, sending operation button display information to the service provider terminal to control the service provider terminal to display the first operation button.

In the application, when receiving a confirmation operation that the service provider confirms the completion of the service order, the service provider terminal sends confirmation operation information to the server, and the server sends operation button display information according to the confirmation operation information, so that the service provider terminal is controlled to display a first operation button for the service provider to operate.

In some embodiments, the method further comprises:

and when process information sent by a service requester terminal according to different processing processes of the service order by the service requester based on the unique identifier of the digital object is received, sending service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing processes.

In the application, in the process that the service requester processes the service order according to the unique identifier of the digital object, the terminal of the service requester sends different process information to the server according to different processing processes, and the server sends the display information of the service ending page to the terminal of the service provider according to the process information so as to control the terminal of the service provider to display the service ending page corresponding to the processing processes, so that the automatic skip of the process is realized, and the operation of the service provider is saved.

In some embodiments, the step of, when receiving progress information transmitted by a service requester terminal in accordance with different processing progresses of the service order by a service requester based on the digital object unique identifier, transmitting service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing progress, includes:

when the process information represents that the service requester does not confirm payment amount, sending first service end page display information to the service provider terminal to control the service provider terminal to display a first service end page corresponding to the processing process; the first service end page comprises a first payment state and a payment mode of the service requester.

In some embodiments, the method further comprises:

and sending operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the first service ending page, wherein the payment mode corresponding to the first operation button is different from the payment mode corresponding to the second operation button.

In the application, when the service requester does not confirm the payment amount, the service requester indicates that the payment is not completed, and considering that the service requester may have a need to change the payment method, the service requester may send the operation button display information to the service provider terminal to control the service provider terminal to display the second operation button on the first service end page.

when the process information represents that the service requester confirms payment amount and does not finish payment, sending second service end page display information to the service provider terminal to control the service provider terminal to display a second service end page corresponding to the processing process; wherein the second service end page includes a second payment status, a payment amount, and a payment method of the service requester.

In some embodiments, the method further comprises:

and sending operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the second service ending page, wherein the payment mode corresponding to the first operation button is different from the payment mode corresponding to the second operation button.

In the application, when the service requester confirms the payment amount but actually does not complete payment, considering that the service requester may have a need to change the payment method, the operation button display information may be sent to the service provider terminal to control the service provider terminal to display the second operation button on the second service end page.

when the process information represents that the service requester confirms the payment amount and finishes the payment, sending third service ending page display information to the service provider terminal to control the service provider terminal to display a third service ending page corresponding to the processing process; wherein the third service end page includes a third payment status, a payment amount, and a payment method of the service requester.

In some embodiments, the method further comprises:

and when a payment mode change request sent by the service provider terminal is received, sending operation button display information to the service provider terminal to control the service provider terminal to display the first operation button in a floating layer mode, wherein the payment mode change request is generated when the service provider selects to change a payment mode corresponding to a second operation button displayed on the service provider terminal into other payment modes.

In the application, when the service provider initially selects the payment method corresponding to the second operation button, if the service requester does not complete payment, and the payment method needs to be changed, the service provider may send a payment method change request to the server through the service provider terminal, and the server controls the service provider terminal to display the first operation button in a floating layer manner according to the payment method change request, so that the service provider changes the payment method corresponding to the second operation button to the payment method corresponding to the first operation button.

In a third aspect, an embodiment of the present invention provides a service order payment apparatus, where the apparatus includes:

the first display module is used for displaying a first operation button when the service order is completed;

a receiving module, configured to receive, in response to an operation of the first operation button by a service provider, a digital object unique identifier associated with the service order sent by a server;

a second display module to display the digital object unique identifier, wherein the digital object unique identifier is to identify a payment link for the service order.

In some embodiments, the first display module is configured to display the first operation button in response to a confirmation operation of the service provider for completion of the service order.

In some embodiments, the apparatus further comprises:

and the third display module is used for displaying a service ending page corresponding to the processing process according to different processing processes of the service order by the service requester based on the unique identifier of the digital object.

In some embodiments, the third display module is configured to display a first service end page when the processing procedure characterizes that the service requestor does not confirm the payment amount; the first service end page comprises a first payment state and a payment mode of the service requester.

In some embodiments, the first display module is further configured to display a second operation button on the first service end page, where a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

In some embodiments, the third display module is configured to display a second service end page when the processing process characterizes that the service requestor has confirmed a payment amount and has not completed payment; wherein the second service end page includes a second payment status, a payment amount, and a payment method of the service requester.

In some embodiments, the first display module is further configured to display a second operation button on the second service end page, where a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

In some embodiments, the third display module is configured to display a third end of service page when the processing procedure characterizes that the service requestor has confirmed a payment amount and completed a payment; wherein the third service end page includes a third payment status, a payment amount, and a payment method of the service requester.

In some embodiments, the first display module is configured to display the first operating button and the second operating button when the service order is completed; the payment mode corresponding to the first operation button is different from the payment mode corresponding to the second operation button;

the device further comprises:

and the fourth display module is used for displaying the first operation button in a floating layer mode when the service provider selects to change the payment mode corresponding to the second operation button into another payment mode.

In some embodiments, the second display module is configured to display the unique identifier of the digital object in a floating layer.

In a fourth aspect, an embodiment of the present application provides another service order payment apparatus, where the apparatus includes:

an identifier generating module, configured to generate a digital object unique identifier associated with a service order when payment means confirmation information transmitted by a service provider terminal in response to an operation of a first operation button by a service provider is received, wherein the first operation button is displayed on the service provider terminal when the service order is completed;

a first sending module for sending the digital object unique identifier to the service provider terminal, wherein the digital object unique identifier displayed on the service provider terminal is used to identify a payment link for the service order.

In some embodiments, the identifier generating module is configured to generate the unique identifier of the digital object according to an order number, an order type, time information, identification information of the service provider, and identification information of the service requester corresponding to the service order.

In some embodiments, the apparatus further comprises:

and a second sending module, configured to, when receiving confirmation operation information sent by the service provider terminal in response to a confirmation operation performed by the service provider on the completion of the service order, send operation button display information to the service provider terminal to control the service provider terminal to display the first operation button.

In some embodiments, the apparatus further comprises:

and a third sending module, configured to, when receiving process information sent by a service requester terminal according to a different processing process of the service order by the service requester based on the unique digital object identifier, send service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing process.

In some embodiments, the third sending module is configured to send first service end page display information to the service provider terminal to control the service provider terminal to display a first service end page corresponding to the processing progress when the progress information indicates that the service requester does not confirm the payment amount; the first service end page comprises a first payment state and a payment mode of the service requester.

In some embodiments, the apparatus further comprises:

a second sending module, configured to send operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the first service end page, where a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

In some embodiments, the third sending module is configured to send second service end page display information to the service provider terminal to control the service provider terminal to display a second service end page corresponding to the processing procedure when the procedure information represents that the service requester has confirmed a payment amount and does not complete payment; wherein the second service end page includes a second payment status, a payment amount, and a payment method of the service requester.

In some embodiments, the apparatus further comprises:

and a second sending module, configured to send operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the second service end page, where a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

In some embodiments, the third sending module is configured to send third service end page display information to the service provider terminal to control the service provider terminal to display a third service end page corresponding to the processing procedure when the process information represents that the service requester has confirmed a payment amount and completed payment; wherein the third service end page includes a third payment status, a payment amount, and a payment method of the service requester.

In some embodiments, the apparatus further comprises:

and a second sending module, configured to send operation button display information to the service provider terminal to control the service provider terminal to display the first operation button in a floating layer manner when receiving a payment method change request sent by the service provider terminal, where the payment method change request is generated when the service provider selects to change a payment method corresponding to a second operation button displayed in the service provider terminal to another payment method.

In a fifth aspect, an embodiment of the present application provides an electronic device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is run, the processor executing the machine-readable instructions to perform the steps of the service order payment method according to any one of the first aspect when executed.

In a sixth aspect, the present application provides a computer-readable storage medium, having stored thereon a computer program, which, when executed by a processor, performs the steps of the service order payment method according to any one of the first aspect.

In a seventh aspect, an embodiment of the present application provides another electronic device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the service order payment method according to any one of the second aspect.

In an eighth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the service order payment method according to any one of the second aspect.

Additional features and advantages of the present application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the embodiments of the present application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

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

FIG. 1 illustrates a block diagram of a service order payment system of some embodiments of the present application;

FIG. 2 illustrates a schematic diagram of exemplary hardware and software components of an electronic device of some embodiments of the present application;

FIG. 3 illustrates a flow chart of a service order payment method provided by an embodiment of the present application;

fig. 4 is a schematic diagram illustrating a display interface of a service provider terminal according to an embodiment of the present application;

fig. 5 is a schematic diagram illustrating a two-dimensional code displayed by a service provider terminal according to an embodiment of the present application;

FIG. 6 illustrates a flow chart of another service order payment method provided by an embodiment of the present application;

fig. 7 is a schematic diagram illustrating a display interface of another service provider terminal provided in an embodiment of the present application;

fig. 8 is a schematic diagram illustrating a display interface of a further service provider terminal provided in an embodiment of the present application;

fig. 9 is a schematic diagram illustrating a display interface of a further service provider terminal provided in an embodiment of the present application;

fig. 10 is a schematic diagram illustrating a display interface of a service requester terminal according to an embodiment of the present application;

fig. 11 is a schematic diagram illustrating a display interface of a further service provider terminal provided in an embodiment of the present application;

fig. 12 is a schematic diagram illustrating a display interface of a further service provider terminal provided in an embodiment of the present application;

fig. 13 is a schematic diagram illustrating a display interface of another service requester terminal provided in an embodiment of the present application;

fig. 14 is a schematic diagram illustrating a display interface of a service requester terminal according to an embodiment of the present application;

fig. 15 is a schematic diagram illustrating a display interface of a service requester terminal according to an embodiment of the present application;

FIG. 16 is a flow chart illustrating yet another service order payment method provided by an embodiment of the present application;

FIG. 17 illustrates a flow chart of yet another service order payment method provided by an embodiment of the present application;

FIG. 18 illustrates a block diagram of a service order payment device provided by an embodiment of the present application;

FIG. 19 illustrates a block diagram of another service order payment device provided by an embodiment of the present application;

FIG. 20 is a block diagram illustrating yet another service order payment apparatus provided by an embodiment of the present application;

FIG. 21 illustrates a block diagram of yet another service order payment device provided by an embodiment of the present application;

FIG. 22 illustrates a block diagram of yet another service order payment apparatus provided by an embodiment of the present application;

fig. 23 shows a block diagram of another service order payment apparatus provided by an embodiment of the present application.

Detailed Description

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

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

To enable those skilled in the art to use the present disclosure, the following embodiments are given in conjunction with a specific application scenario, "taxi calling service". It will be apparent to those skilled in the art that the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the application. Although the present application is described primarily with respect to a taxi cab service, it should be understood that this is merely one exemplary embodiment. The application can be applied to any other traffic type. For example, the present application may be applied to different transportation system environments, including terrestrial, marine, or airborne, among others, or any combination thereof. The vehicle of the transportation system may include a private car, a tailgating vehicle, a bus, a train, a bullet train, a high speed rail, a subway, a ship, an airplane, a spacecraft, a hot air balloon, or an unmanned vehicle, etc., or any combination thereof. The present application may also include any service system requiring code scanning payment orders, for example, systems for sending and/or receiving couriers, service systems for both buyer and seller transactions. Applications of the system or method of the present application may include web pages, plug-ins for browsers, client terminals, customization systems, internal analysis systems, or artificial intelligence robots, among others, or any combination thereof.

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

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

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

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

One aspect of the present application relates to a service order payment method, which may include that when a service order is completed, a service provider operates a first operation button displayed on a terminal of the service provider to receive a digital object unique identifier sent by a server and associated with the service order, and a service requester pays for the service order according to the digital object unique identifier, so that association between payment conditions of the service requester and the service order is achieved, and the server is facilitated to know payment details of the service order.

It is noted that, before the application of the present application, among passengers who call a taxi service online using a taxi calling APP, there is a higher proportion of passengers who select an order settlement method for cash payment. However, due to the popularization of mobile payment tools, many users are not used to carry a wallet, so although taxi drivers choose cash payment on APPs, passengers actually scan two-dimensional codes of the taxi drivers by using third-party software (such as WeChat, Payment treasures and the like) to pay, and the whole payment process is troublesome. A taxi driver needs to select a cash payment button on a bill confirmation page, then selects a taxi-receiving button on a journey end page, opens a two-dimensional code on an APP front page through a taxi-receiving fee button and displays the two-dimensional code to a passenger, the operation flow of the driver is long, and the waiting cost of the passenger is high; for the server, due to the separation of the order of taking a car and the code scanning payment link, the order of the online journey is in one data table, the order of the code scanning payment is in the other data table, the order of the online journey and the order of the code scanning payment are not associated, namely, the two events which occur in the same journey, namely passenger taking a car and passenger payment are not associated, so that the server is inconvenient to carry out data statistics and learn the details of the order. In an actual payment scene, when a taxi driver does not know a code scanning payment process of an on-line order, the passenger usually selects to display a WeChat card or a Paibao card for scanning, so that the payment condition cannot be traced once a service problem occurs subsequently. However, the service order payment method provided by the application can help the taxi driver provide the passenger with the digital object unique identifier associated with the service order, and after the passenger pays according to the digital object unique identifier, the server can know the payment mode, payment time, payment amount and corresponding journey of the service order, and once disputes follow-up happens, the server is well documented.

FIG. 1 is a block diagram of a service order payment system 100 of some embodiments of the present application. For example, the service order payment system 100 may be an online transportation service platform for transportation services such as taxis, designated driving services, driver rentals, or any combination thereof; the method can also be used for other Internet service platforms with code scanning payment online order scenes such as express delivery service, take-out service and the like.

The service order payment system 100 may include one or more of a server 110, a network 120, a service requester terminal 130, a service provider terminal 140, and a database 150, and the server 110 may include a processor therein that performs instruction operations.

In some embodiments, the server 110 may be a single server or a group of servers. The set of servers can be centralized or distributed (e.g., the servers 110 can be a distributed system). In some embodiments, the server 110 may be local or remote to the terminal. For example, the server 110 may access information and/or data stored in the service requester terminal 130, the service provider terminal 140, or the database 150, or any combination thereof, via the network 120. As another example, the server 110 may be directly connected to at least one of the service requester terminal 130, the service provider terminal 140, and the database 150 to access stored information and/or data. In some embodiments, the server 110 may be implemented on a cloud platform; by way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud (community cloud), a distributed cloud, an inter-cloud, a multi-cloud, and the like, or any combination thereof. In some embodiments, the server 110 may be implemented on an electronic device 200 having one or more of the components shown in FIG. 2 in the present application.

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

Network 120 may be used for the exchange of information and/or data. In some embodiments, one or more components in the service order payment system 100 (e.g., the server 110, the service requestor terminal 130, the service provider terminal 140, and the database 150) may send information and/or data to other components. For example, the server 110 may obtain a service request from the service requester terminal 130 via the network 120. In some embodiments, the network 120 may be any type of wired or wireless network, or combination thereof. Merely by way of example, Network 120 may include a wired Network, a Wireless Network, a fiber optic Network, a telecommunications Network, an intranet, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a Public Switched Telephone Network (PSTN), a bluetooth Network, a ZigBee Network, a Near Field Communication (NFC) Network, or the like, or any combination thereof. In some embodiments, network 120 may include one or more network access points. For example, network 120 may include wired or wireless network access points, such as base stations and/or network switching nodes, through which one or more components of service order payment system 100 may connect to network 120 to exchange data and/or information.

In some embodiments, the user of the service requestor terminal 130 may be someone other than the actual demander of the service. For example, the user a of the service requester terminal 130 may use the service requester terminal 130 to initiate a service request for the service actual demander B (for example, the user a may call a car for his friend B), or receive service information or instructions from the server 110. In some embodiments, the user of the service provider terminal 140 may be the actual provider of the service or may be another person than the actual provider of the service. For example, user C of the service provider terminal 140 may use the service provider terminal 140 to receive a service request serviced by the service provider entity D (e.g., user C may pick up an order for driver D employed by user C), and/or information or instructions from the server 110. In some embodiments, "service requester" and "service requester terminal" may be used interchangeably, and "service provider" and "service provider terminal" may be used interchangeably.

In some embodiments, the service requester terminal 130 may comprise a mobile device, a tablet computer, a laptop computer, or a built-in device in a motor vehicle, etc., or any combination thereof. In some embodiments, the mobile device may include a smart home device, a wearable device, a smart mobile device, a virtual reality device, an augmented reality device, or the like, or any combination thereof. In some embodiments, the smart home devices may include smart lighting devices, control devices for smart electrical devices, smart monitoring devices, smart televisions, smart cameras, or walkie-talkies, or the like, or any combination thereof. In some embodiments, the wearable device may include a smart bracelet, a smart lace, smart glass, a smart helmet, a smart watch, a smart garment, a smart backpack, a smart accessory, and the like, or any combination thereof. In some embodiments, the smart mobile device may include a smartphone, a Personal Digital Assistant (PDA), a gaming device, a navigation device, or a point of sale (POS) device, or the like, or any combination thereof. In some embodiments, the virtual reality device and/or the augmented reality device may include a virtual reality helmet, virtual reality glass, a virtual reality patch, an augmented reality helmet, augmented reality glass, an augmented reality patch, or the like, or any combination thereof. For example, the virtual reality device and/or augmented reality device may include various virtual reality products and the like. In some embodiments, the built-in devices in the motor vehicle may include an on-board computer, an on-board television, and the like. In some embodiments, the service requester terminal 130 may be a device having a location technology for locating the location of the service requester and/or service requester terminal.

In some embodiments, the service provider terminal 140 may be a similar or identical device as the service requestor terminal 130. In some embodiments, the service provider terminal 140 may be a device with location technology for locating the location of the service provider and/or the service provider terminal. In some embodiments, the service requester terminal 130 and/or the service provider terminal 140 may communicate with other locating devices to determine the location of the service requester, service requester terminal 130, service provider, or service provider terminal 140, or any combination thereof. In some embodiments, the service requester terminal 130 and/or the service provider terminal 140 may transmit the location information to the server 110.

Database 150 may store data and/or instructions. In some embodiments, the database 150 may store data obtained from the service requester terminal 130 and/or the service provider terminal 140. In some embodiments, database 150 may store data and/or instructions for the exemplary methods described herein. In some embodiments, database 150 may include mass storage, removable storage, volatile Read-write Memory, or Read-Only Memory (ROM), among others, or any combination thereof. By way of example, mass storage may include magnetic disks, optical disks, solid state drives, and the like; removable memory may include flash drives, floppy disks, optical disks, memory cards, zip disks, tapes, and the like; volatile read-write Memory may include Random Access Memory (RAM); the RAM may include Dynamic RAM (DRAM), Double data Rate Synchronous Dynamic RAM (DDR SDRAM); static RAM (SRAM), Thyristor-Based Random Access Memory (T-RAM), Zero-capacitor RAM (Zero-RAM), and the like. By way of example, ROMs may include Mask Read-Only memories (MROMs), Programmable ROMs (PROMs), Erasable Programmable ROMs (PERROMs), Electrically Erasable Programmable ROMs (EEPROMs), compact disk ROMs (CD-ROMs), digital versatile disks (ROMs), and the like. In some embodiments, database 150 may be implemented on a cloud platform. By way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, across clouds, multiple clouds, or the like, or any combination thereof.

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

In some embodiments, one or more components in the service order payment system 100 (e.g., the server 110, the service requestor terminal 130, the service provider terminal 140, etc.) may have access to the database 150. In some embodiments, one or more components in the service order payment system 100 may read and/or modify information related to the service requestor, the service provider, or the public, or any combination thereof, when certain conditions are met. For example, server 110 may read and/or modify information for one or more users after receiving a service request. As another example, the service provider terminal 140 may access information related to the service requester when receiving the service request from the service requester terminal 130, but the service provider terminal 140 may not modify the related information of the service requester.

In some embodiments, the exchange of information by one or more components in the service order payment system 100 may be accomplished by requesting a service. The object of the service request may be any product. In some embodiments, the product may be a tangible product or a non-physical product. Tangible products may include food, pharmaceuticals, commodities, chemical products, appliances, clothing, automobiles, homes, or luxury goods, and the like, or any combination thereof. The non-material product may include a service product, a financial product, a knowledge product, an internet product, or the like, or any combination thereof. The internet product may include a stand-alone host product, a network product, a mobile internet product, a commercial host product, an embedded product, or the like, or any combination thereof. The internet product may be used in software, programs, or systems of the mobile terminal, etc., or any combination thereof. The mobile terminal may include a tablet, a laptop, a mobile phone, a Personal Digital Assistant (PDA), a smart watch, a Point of sale (POS) device, a vehicle-mounted computer, a vehicle-mounted television, a wearable device, or the like, or any combination thereof. The internet product may be, for example, any software and/or application used in a computer or mobile phone. The software and/or applications may relate to social interaction, shopping, transportation, entertainment time, learning, or investment, or the like, or any combination thereof. In some embodiments, the transportation-related software and/or applications may include travel software and/or applications, vehicle dispatch software and/or applications, mapping software and/or applications, and the like. In the vehicle scheduling software and/or application, the vehicle may include a horse, a carriage, a human powered vehicle (e.g., unicycle, bicycle, tricycle, etc.), an automobile (e.g., taxi, bus, privatege, etc.), a train, a subway, a ship, an airplane (e.g., airplane, helicopter, space shuttle, rocket, hot air balloon, etc.), etc., or any combination thereof.

Fig. 2 illustrates a schematic diagram of exemplary hardware and software components of an electronic device 200 of a server 110, a service requester terminal 130, a service provider terminal 140, which may implement the concepts of the present application, according to some embodiments of the present application. For example, the processor 220 may be used on the electronic device 200 and to perform the functions herein.

The electronic device 200 may be a general purpose computer or a special purpose computer, both of which may be used to implement the service order payment method of the present application. Although only a single computer is shown, for convenience, the functions described herein may be implemented in a distributed fashion across multiple similar platforms to balance processing loads.

For example, the electronic device 200 may include a network port 210 connected to a network, one or more processors 220 for executing program instructions, a communication bus 230, and a different form of storage medium 240, such as a disk, ROM, or RAM, or any combination thereof. Illustratively, the computer platform may also include program instructions stored in ROM, RAM, or other types of non-transitory storage media, or any combination thereof. The method of the present application may be implemented in accordance with these program instructions. The electronic device 200 also includes an Input/Output (I/O) interface 250 between the computer and other Input/Output devices (e.g., keyboard, display screen).

For ease of illustration, only one processor 220 is depicted in the electronic device 200. However, it should be noted that the electronic device 200 in the present application may also include a plurality of processors 220, and thus the steps performed by one processor 220 described in the present application may also be performed by a plurality of processors 220 in combination or individually. For example, if the processor 220 of the electronic device 200 executes step a and step B, it should be understood that step a and step B may also be executed by two different processors 220 together or executed in one processor 220 separately. For example, a first processor performs step a and a second processor performs step B, or the first processor and the second processor perform steps a and B together.

Fig. 3 is a flowchart illustrating a service order payment method according to an embodiment of the present application. The main execution subject of the method is a service provider terminal, as shown in fig. 3, the method includes:

s301, when the service order is completed, a first operation button is displayed.

The first operation button is equivalent to a selection entrance of a payment mode, and the service provider can select the corresponding payment mode by operating the first operation button.

Alternatively, the service provider terminal may display the first operation button in response to a confirmation operation of the service provider for completion of the service order. For example, the service provider may confirm the completion of the service order through a slide operation.

In order to provide diversified order payment modes for the service requester, a first operation button and a second operation button can be displayed when the service order is completed, wherein the payment mode corresponding to the first operation button is different from the payment mode corresponding to the second operation button. The number of the second operation buttons may be one or more, which is not limited in the present application. In this way, the service provider can operate the first operation button or the second operation button according to the requirement of the service requester, so that the service requester can pay for the service order according to the payment method corresponding to the first operation button or the payment method corresponding to the second operation button.

Taking a taxi service as an example, referring to fig. 4, after a driver sends out a taxi passenger to a destination, the driver slides the "destination" on a display page of the driver side APP to make the page enter a bill confirmation page, and a first operation button (i.e., "code scanning payment" button) and a second operation button (i.e., "cash payment" button, "30-yuan payment to passenger line" button) can be displayed on the bill confirmation page. The 30 Yuan to the passenger's line collection button corresponds to the on-line payment mode, and when the driver selects the on-line payment mode, the driver is required to input the amount of the fare.

It should be noted that, in practical applications, the entering of the confirmation bill page may not be triggered by the sliding operation of the driver, for example, the service provider terminal may detect the current location in real time, and when the current location is detected as the passenger destination, automatically jump to the confirmation bill page displaying the first operation button and the second operation button by interacting with the server.

S302, responding to the operation of the first operation button by the service provider, receiving the unique identifier of the digital object associated with the service order sent by the server.

The unique identifier of the digital object comprises an order number, an order type, time information, identification information of a service provider and identification information of a service requester corresponding to the service order.

Optionally, the service provider may select a payment method corresponding to the first operation button by clicking the first operation button, and the service provider terminal obtains the unique identifier of the digital object associated with the service order sent by the server by responding to the click operation of the service provider on the first operation button. That is, the unique identifier of the digital object is generated by the server according to the order number, the order type, the time information, the identification information of the service provider, the identification information of the service requester and other related data corresponding to the service order, and is issued to the terminal of the service provider, so that the association between the unique identifier of the digital object and the service order is realized.

For example, when the service order is a taxi order, then the digital object unique identifier may include data in the taxi order such as order number, driver ID, passenger ID, starting point, time (pickup time, travel time, order end time, etc.), type of order (real-time order/reservation order), etc.

S303, displaying the unique identifier of the digital object, wherein the unique identifier of the digital object is used for identifying the payment link of the service order, so that the service requester can pay for the service order according to the unique identifier of the digital object displayed on the service provider terminal.

Optionally, after receiving the unique identifier of the digital object issued by the server, the service provider terminal may display the unique identifier of the digital object in a floating layer manner.

Alternatively, the digital object unique identifier may be a two-dimensional code or a bar code, and the service requester may pay for the service order by scanning the digital object unique identifier.

In this embodiment, the unique identifier of the digital object may be valid at all times and may be code-swiped if screen-shot or picture-taking remains; however, if the service order is in a paid status, the code scan prompts "the order is paid".

Taking taxi service as an example, after a driver clicks a 'code scanning payment' button in fig. 4, the driver end APP displays the two-dimensional code shown in fig. 5, and the two-dimensional code can be amplified by clicking the two-dimensional code. The driver can be reminded to remind the driver to inform the passenger of the amount of money and collect the fare above the two-dimensional code, the driver can be reminded to remind the driver to use a payment treasure or a WeChat for payment after the passenger pays successfully, the journey is automatically ended after the passenger pays successfully, the driver shows the two-dimensional code to the passenger, and the passenger can pay the service order by scanning the two-dimensional code.

Therefore, according to the service order payment method provided by the embodiment of the application, the unique identifier of the digital object sent by the server can be automatically acquired through the operation of the first operation button by the service provider, and compared with a code scanning payment mode in the prior art, the operation process is simplified, the operation experience of the service provider is improved, and the waiting cost of the service requester is reduced; because the digital object unique identifier is associated with the service order, after the service requester pays for the service order according to the digital object unique identifier, the server can obtain the payment details of the service order, and once payment disputes occur subsequently, the server is well documented.

In implementation, in the process that the service requester pays the service order according to the unique identifier of the digital object, the service provider terminal needs to automatically skip the flow through the payment process of the service requester, so as to save the operation of the service provider. Based on this, as shown in fig. 6, after S303, the method further includes:

s304, displaying a service ending page corresponding to the processing progress according to different processing progresses of the service request party to the service order based on the unique identifier of the digital object.

That is, in the process of processing the service order by the service requester according to the unique identifier of the digital object, the service provider terminal can display different service end pages for different processing processes, so as to implement automatic skip of the flow, thereby saving the operation of the service provider.

In a possible embodiment, the first service end page is displayed when the processing procedure characterizes that the service requester does not confirm the payment amount; the first service end page comprises a first payment state and a payment mode of the service requester.

Considering that the service requester has a need to change the payment method in the process of paying for the service order, a second operation button may be displayed on the first service end page, where the payment method corresponding to the first operation button is different from the payment method corresponding to the second operation button. When the service provider terminal displays the first service end page, the service provider terminal indicates that the service requester does not confirm the payment amount and also indicates that the payment is not finished, and when the service requester wants to change the payment mode, the service provider can change the current payment mode from the payment mode corresponding to the first operation button to the payment mode corresponding to the second operation button by operating the second operation button displayed on the first service end page.

For example, when the driver wants to go to the next page as soon as possible on the two-dimensional code display page of fig. 5, or the passenger actually does not scan the two-dimensional code, chooses to scan a physical card, or wants to change to cash payment, the driver can click the upper right corner of the two-dimensional code floating layer to close. Referring to fig. 7, when the driver closes the two-dimensional code, if the passenger does not scan the two-dimensional code or does not confirm the payment amount after scanning the two-dimensional code, the "code scanning payment incomplete" and the "cash payment" buttons (i.e., the second operation buttons) are displayed on the first service end page. As can be seen, in the first service end page, the first payment status of the service requester may be an incomplete status, and the payment method of the service requester may be code scanning payment.

When the passenger does not finish the payment, if the passenger wants to change the payment mode, the driver can click a 'cash payment' button to change the code scanning payment mode into a cash payment mode; when the driver clicks the "cash payment" button, the page will display a pop-up window as shown in fig. 8 and prompt the driver to "please notify the passenger of the amount of money and collect cash to the passenger", when the driver has collected cash to the passenger, the driver may click "cash collected"; when the driver clicks on "cash received", referring to fig. 9, the page displays "order paid in cash".

It should be noted that, in this embodiment, when the service requester has not confirmed the payment amount, the cashier for recording the bill information records the bill of the service order as a code scanning payment to-be-paid bill with an amount of 0.

In another possible embodiment, when the processing process characterizes that the service requester has confirmed the payment amount and has not completed the payment, displaying a second service end page; the second service ending page comprises a second payment state, payment amount and payment mode of the service requester.

Considering that the service requester has a need to change the payment method in the process of paying for the service order, a second operation button may be displayed on the second service end page, where the payment method corresponding to the first operation button is different from the payment method corresponding to the second operation button. When the service provider terminal displays the second service end page, the service requester terminal indicates that the payment amount is confirmed but the payment is not actually completed, and when the service requester terminal wants to change the payment mode, the service provider terminal can change the current payment mode from the payment mode corresponding to the first operation button to the payment mode corresponding to the second operation button by operating the second operation button displayed on the second service end page.

For example, referring to fig. 10, when the passenger uses the WeChat or Payment pal to scan the two-dimensional code, and then inputs the amount 35 (for example only, any number N) dollars, and clicks "confirm Payment", the cashier will receive the amount data, and then change the price of the 0 dollar bill to be scanned for payment generated before the passenger does not confirm the payment amount. At this time, the "N-yuan to be scanned for code payment" and "cash payment" buttons (i.e., second operation buttons) are displayed on the second service end page. As can be seen, in the second service end page, the second payment status of the service requester may be a to-be-paid status, and the payment method of the service requester may be code-scanning payment. And after the passenger finishes payment, the page of the driver side APP displays the code scanning payment N yuan, and the cashier desk records the bill state of the service order as the code scanning payment N yuan.

For example, referring to fig. 11, in a normal flow, when a passenger scans a two-dimensional code and completes payment, the floating layer of the two-dimensional code will automatically disappear and enter an end-of-travel page, which displays a scanned-code payment of 30 yuan, 30 for the passenger to scan the code input amount.

In another possible embodiment, when the processing procedure characterizes that the service requester has confirmed the payment amount and completed the payment, a third service end page is displayed; the third service ending page comprises a third payment state, payment amount and payment mode of the service requester.

In the application, when the service requester really completes payment of the service order, a third service end page is displayed on the service provider terminal, and a third payment state, payment amount and payment mode of the service requester are displayed on the third service end page. The third service ending page may refer to the page shown in fig. 11, where the third payment status of the service requester is a paid status, the payment method of the service requester is a code scanning payment, and the payment amount of the service requester is 30 yuan.

In practical applications, when the service provider initially selects not the payment method corresponding to the first operation button but another payment method (for example, selects the payment method corresponding to the second operation button), the service requester may request to change the payment method before the payment is completed.

Based on this, when the service provider selects to change the payment method corresponding to the second operation button to another payment method, the first operation button is displayed in a floating manner.

That is, when the service order is finished, the service provider terminal may display the first operation button and the second operation button, so that the service provider may select different payment methods, and if the service provider initially selects the payment method corresponding to the second operation button, and if the service requester does not finish payment, the service provider may display the first operation button in a floating layer manner, so that the service provider changes the payment method corresponding to the second operation button to the payment method corresponding to the first operation button.

For example, referring to fig. 12, when the passenger requests a scan payment or cash payment after the driver initially clicks the "online payment" button (i.e., the second operation button), the "change payment method" button may be clicked on the trip end page, and the "scan payment" button (i.e., the first operation button) may be displayed on the change payment method page in a floating manner. In practical application, in order to provide more optional payment modes for passengers, after a driver clicks a 'change payment mode' button on a travel end page, a 'cash payment' button and a 'code scanning payment' button can be displayed in a floating layer mode at the same time so that the driver can select a specific payment mode.

It should be noted that, for the passenger side APP, when the driver arrives at the destination but has not initiated cash payment, online payment or code scanning payment, the passenger side APP will always display the journey. When the driver clicks the 'code payment by scanning' button, the cashier desk generates a 0-element bill to be paid by scanning the code, the passenger APP displays a 'payment entrance' page shown in figure 13, the page displays that the travel is finished and the bus fee paid by scanning the code is to be paid, and the passenger is reminded to use WeChat or Payment treasured to scan the two-dimensional code of the driver for payment. If the passenger uses the WeChat or Payment treasure to scan the code to input the amount and clicks to confirm the payment, but the payment is not actually finished, the passenger end APP jumps to a payment component page shown in the figure 14 from a payment inlet page, the page prompts the passenger to request to scan the driver two-dimensional code to pay by using the WeChat or Payment treasure, and an unpaid code scanning payment order is displayed; the floating layer of the 'payment component' can be forked off, a 'payment entrance' page is displayed after the fork off, and a home page can be returned through the 'payment entrance' page; when the passenger does not finish payment, other payment methods can be used, such as 'in-vehicle card payment by sweeping' or 'cash payment'; if the passenger disagrees with the bill for the code scan (e.g., thinks the driver has maliciously initiated the payment), the "fee question" can be clicked on to a service feedback page.

Referring to fig. 15, when the passenger successfully scans the code payment using wechat or pay pal, the passenger APP displays the scanned code payment N (for example, N ═ 35) yuan, and the cashier registers the bill status as paid. The display content of the passenger terminal APP is subject to the final actual payment mode, namely if the driver changes the cash payment mode into the cash payment mode, the cash payment is displayed.

In the embodiment, when a passenger selects WeChat or Payment to perform two-dimensional code scanning payment, and after the passenger inputs the amount of the fare and finishes payment, the driver side APP and the passenger side APP display that the taxi taking order is subjected to code scanning payment, and after the passenger finishes payment, the driver side APP enters an order ending page and can display the payment amount and the paid state; for the server, the taxi order is displayed as a code scanning payment (corresponding to an online payment and a cash payment) in the order payment mode, and is displayed as an online order (corresponding to a raise order) in the order source in the code scanning payment.

Therefore, the service order payment method provided by the embodiment of the application realizes the skipping of the flow through the payment process of the service requester, thereby saving the operation of the service provider and improving the operation experience of the service provider; the payment method has the advantages that diversified selective payment methods are provided for the service requester, the payment method can be changed according to actual conditions in the payment process of the service order, the whole payment process is smooth, and better experience is provided for the service requester and the service provider.

Fig. 16 is a flow chart illustrating another service order payment method provided by the embodiment of the application. The execution subject of the method is a server, as shown in fig. 16, the method includes:

s401, when receiving the confirmation operation information sent by the service provider terminal in response to the confirmation operation of the service provider for the completion of the service order, sends operation button display information to the service provider terminal to control the service provider terminal to display the first operation button.

In actual use, in order to provide diversified order payment manners to the service requester, the server may transmit operation button display information to the service provider terminal to control the service provider terminal to display the first operation button and the second operation button upon receiving confirmation operation information transmitted by the service provider terminal in response to a confirmation operation of the service provider for completion of the service order.

Taking the taxi calling service as an example, still referring to fig. 4, after the driver sends out the taxi passenger to the destination, the driver slides on the display page of the driver side APP to reach the destination, at the moment, the service provider terminal sends confirmation operation information to the server according to the sliding operation of the driver, the server sends operation button display information according to the confirmation operation information, the service provider terminal jumps the page to a bill confirmation page according to the received operation button display information, the confirmation bill page is displayed with a first operation button (namely, a ' code scanning payment ' button) and a second operation button (namely, a ' cash payment ' button, a ' 30-yuan of money to be collected on the passenger's line ' button), the 30 Yuan payment to the passenger line button corresponds to the online payment mode, and the driver selects the corresponding payment mode by operating the first operation button or the second operation button.

S402, when receiving payment method confirmation information sent by the service provider terminal in response to an operation of a first operation button by the service provider, the first operation button being displayed on the service provider terminal upon completion of the service order, generating a digital object unique identifier associated with the service order.

In this embodiment, the service provider causes the service provider terminal to transmit payment means confirmation information to the server by operating a first operation button displayed on the service provider terminal, and the server generates the digital object unique identifier associated with the service order according to the payment means confirmation information.

Specifically, the server may generate the unique identifier of the digital object according to an order number, an order type, time information, identification information of a service provider, and identification information of a service requester corresponding to the service order. In this manner, association of the digital object unique identifier with the service order may be accomplished.

Step S403, sending the digital object unique identifier to the service provider terminal, wherein the digital object unique identifier displayed on the service provider terminal is used for identifying a payment link of the service order, so that the service requester pays for the service order according to the digital object unique identifier displayed on the service provider terminal.

In this embodiment, the digital object unique identifier may be a two-dimensional code or a bar code. The server sends the generated unique identifier of the digital object associated with the service order to the terminal of the service provider, when the service requester pays for the service order according to the unique identifier of the digital object, the server can obtain the payment details of the service order, and once payment disputes occur subsequently, the server is well documented.

In the process that the service requester pays the service order according to the unique identifier of the digital object, the server needs to control the service provider terminal to automatically skip the flow in real time according to the payment process of the service requester on the service order, so that the operation of the service provider is saved.

Based on this, as shown in fig. 17, after S403, the method further includes:

s404, when receiving the process information sent by the service requester terminal according to the different processing processes of the service order by the service requester based on the unique identifier of the digital object, sending service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing processes.

That is, in the process that the service requester pays the service order according to the unique identifier of the digital object, the terminal of the service requester sends different process information to the server according to different processing processes, and the server sends the service end page display information to the terminal of the service provider according to the process information so as to control the terminal of the service provider to display the service end page corresponding to the processing processes, thereby realizing automatic skip of the flow and saving the operation of the service provider.

In a possible embodiment, when the process information indicates that the service requester does not confirm the payment amount, sending first service end page display information to the service provider terminal to control the service provider terminal to display a first service end page corresponding to the processing process; the first service end page comprises a first payment state and a payment mode of the service requester.

In the first service end page, the first payment status of the service requester may be an incomplete status, and the payment method of the service requester may be code scanning payment.

Considering that the service requester has a need to change the payment method in the process of paying the service order, the server may send operation button display information to the service provider terminal to control the service provider terminal to display the second operation button on the first service end page, where the payment method corresponding to the first operation button is different from the payment method corresponding to the second operation button.

In this embodiment, when the service requester does not confirm the payment amount, it indicates that the service requester has not completed payment, and considering that the service requester may have a need to change the payment method, the service requester may send operation button display information to the service provider terminal to control the service provider terminal to display the second operation button on the first service end page.

In another possible implementation, when the process information represents that the service requester confirms the payment amount and does not complete the payment, sending second service end page display information to the service provider terminal to control the service provider terminal to display a second service end page corresponding to the processing process; the second service ending page comprises a second payment state, payment amount and payment mode of the service requester.

In the second service end page, the second payment status of the service requester may be a to-be-paid status, and the payment mode of the service requester may be code scanning payment.

Considering that the service requester has a need to change the payment method in the process of paying the service order, the server may send operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the second service end page, where the payment method corresponding to the first operation button is different from the payment method corresponding to the second operation button.

In another possible implementation, when the process information represents that the service requester has confirmed the payment amount and completes the payment, third service end page display information is sent to the service provider terminal to control the service provider terminal to display a third service end page corresponding to the processing process; the third service ending page comprises a third payment state, payment amount and payment mode of the service requester.

In the third service end page, the third payment status of the service requester may be a paid status, the payment method of the service requester may be code scanning payment, and the payment amount of the service requester may be an input amount of the service requester.

In practical applications, when the service provider initially selects a payment method that is not corresponding to the first operation button, the service requester may request to change the payment method before the payment is completed.

Based on this, when a payment method change request which is generated when the service provider selects to change the payment method corresponding to the second operation button displayed on the service provider terminal to another payment method is received, operation button display information is transmitted to the service provider terminal to control the service provider terminal to display the first operation button in a floating manner.

As can be seen, in another service order payment method provided by the present application, a service provider operates a first operation button displayed on a terminal of the service provider, so that the terminal of the service provider sends payment method confirmation information to a server, the server generates a unique digital object identifier associated with a service order according to the payment method confirmation information, and issues the unique digital object identifier to the terminal of the service provider, and since the unique digital object identifier is associated with the service order, after a service requester pays the service order according to the unique digital object identifier, the server can obtain payment details of the service order, and once payment disputes occur subsequently, the server is well documented. In the process of paying the order by the service requester, the skip of the payment process control flow through the service requester is realized, so that the operation of the service provider is saved, and the operation experience of the service provider is improved; the payment method has the advantages that diversified selective payment methods are provided for the service requester, the payment method can be changed according to actual conditions in the payment process of the service order, the whole payment process is smooth, and better experience is provided for the service requester and the service provider.

Fig. 18 is a block diagram illustrating a service order payment apparatus according to an embodiment of the present application, which implements functions corresponding to the steps performed by the above method. The service order payment device may be understood as the service provider terminal, or a processor of the service provider terminal, or may be understood as a component that is independent from the service provider terminal or the processor and implements the functions of the present application under the control of the service provider terminal, as shown in fig. 18, the service order payment device may include a first display module 510, a receiving module 520, and a second display module 530.

The first display module 510 may be configured to display a first operation button when the service order is completed.

Optionally, the first display module 510 may be specifically configured to display a first operation button in response to a confirmation operation of the service provider on completion of the service order.

Optionally, the first display module 510 may be further specifically configured to display a first operation button and a second operation button when the service order is completed; and the payment mode corresponding to the first operation button is different from the payment mode corresponding to the second operation button.

The receiving module 520 may be configured to receive the unique identifier of the digital object associated with the service order sent by the server in response to the operation of the first operation button by the service provider.

Alternatively, the digital object unique identifier may be a two-dimensional code or a bar code; the unique identifier of the digital object comprises an order number, an order type, time information, identification information of a service provider and identification information of a service requester corresponding to the service order.

The second display module 530 may be configured to display the digital object unique identifier, wherein the digital object unique identifier is used to identify a payment link for the service order, such that the service requester pays for the service order according to the digital object unique identifier displayed on the service provider terminal.

Optionally, the second display module 530 may be specifically configured to display the unique identifier of the digital object in a floating layer manner.

Optionally, referring to fig. 19, the apparatus may further include a third display module 540, and the third display module 540 may be configured to display a service end page corresponding to a processing progress according to different processing progresses of the service order by the service requester based on the digital object unique identifier.

In a possible implementation, the third display module 540 may be specifically configured to display a first service end page when the processing procedure characterizes that the service requester does not confirm the payment amount; the first service ending page comprises a first payment state and a payment mode of a service requester; the first display module 510 may be further specifically configured to display a second operation button on the first service end page, where a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

In another possible implementation, the third display module 540 may be specifically configured to display a second service end page when the processing process represents that the service requester has confirmed the payment amount and has not completed the payment; the second service ending page comprises a second payment state, payment amount and payment mode of the service requester; the first display module 510 may be further specifically configured to display a second operation button on the second service end page, where a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

In another possible implementation, the third display module 540 may be specifically configured to display a third service end page when the processing procedure represents that the service requester has confirmed the payment amount and completed the payment; the third service ending page comprises a third payment state, payment amount and payment mode of the service requester.

Optionally, referring to fig. 20, the apparatus may further include a fourth display module 550, and the fourth display module 550 may be configured to display the first operation button in a floating manner when the service provider selects to change the payment method corresponding to the second operation button to another payment method.

It should be noted that, in practical applications, the first display module 510, the second display module 530, the third display module 540 and the fourth display module 550 may be different modules or may be the same module, which is not limited in this embodiment of the present application.

Fig. 21 is a block diagram illustrating a service order payment apparatus according to another embodiment of the present application, which implements functions corresponding to the steps performed by the above method. The service order payment apparatus may be understood as the server or the processor of the server, or may be understood as a component that is independent from the server or the processor and implements the functions of the present application under the control of the server, as shown in fig. 21, the service order payment apparatus may include an identifier generating module 610 and a first sending module 620.

The identifier generation module 610 may be configured to generate a digital object unique identifier associated with the service order upon receiving payment means confirmation information transmitted by the service provider terminal in response to operation of a first operation button by the service provider, wherein the first operation button is displayed on the service provider terminal upon completion of the service order.

In this embodiment, the identifier generating module 610 may be specifically configured to generate the unique identifier of the digital object according to an order number, an order type, time information, identification information of a service provider, and identification information of a service requester corresponding to a service order.

Alternatively, the unique identifier of the digital object may be a two-dimensional code or a bar code.

The first transmitting module 620 may be configured to transmit the digital object unique identifier to the service provider terminal, wherein the digital object unique identifier displayed on the service provider terminal is used to identify a payment link for the service order for the service requester to pay for the service order according to the digital object unique identifier displayed on the service provider terminal.

Optionally, referring to fig. 22, the apparatus may further include a second sending module 630, and the second sending module 630 may be configured to send operation button display information to the service provider terminal to control the service provider terminal to display the first operation button when receiving confirmation operation information sent by the service provider terminal in response to a confirmation operation of the service provider for completion of the service order.

Optionally, referring to fig. 23, the apparatus may further include a third sending module 640, and the third sending module 640 may be configured to, when receiving process information sent by the service requester terminal according to different processing processes of the service order by the service requester based on the digital object unique identifier, send service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing processes.

In a possible implementation manner, the third sending module 640 may be specifically configured to send, to the service provider terminal, first service end page display information to control the service provider terminal to display a first service end page corresponding to the processing procedure when the process information indicates that the service requester does not confirm the payment amount; the first service end page comprises a first payment state and a payment mode of the service requester. The second sending module 630 may be further configured to send operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the first service end page, where a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

In another possible implementation, the third sending module 640 may be specifically configured to send, to the service provider terminal, second service end page display information to control the service provider terminal to display a second service end page corresponding to the processing procedure when the process information represents that the service requester has confirmed the payment amount and does not complete the payment; the second service ending page comprises a second payment state, payment amount and payment mode of the service requester. The second sending module 630 may be further configured to send operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the second service end page, where a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

In another possible implementation, the third sending module 640 may be specifically configured to, when the process information represents that the service requester has confirmed the payment amount and completed the payment, send third service end page display information to the service provider terminal to control the service provider terminal to display a third service end page corresponding to the processing process; the third service ending page comprises a third payment state, payment amount and payment mode of the service requester.

Optionally, the second sending module 630 is further configured to send operation button display information to the service provider terminal to control the service provider terminal to display the first operation button in a floating layer manner when receiving a payment method change request sent by the service provider terminal, where the payment method change request is generated when the service provider selects to change the payment method corresponding to the second operation button displayed in the service provider terminal to another payment method.

It should be noted that, in practical applications, the first sending module 620, and the third sending module 640 may be different modules or may be the same module, and this is not limited in this embodiment of the application.

The modules may be connected or in communication with each other via a wired or wireless connection. The wired connection may include a metal cable, an optical cable, a hybrid cable, etc., or any combination thereof. The wireless connection may comprise a connection over a LAN, WAN, bluetooth, ZigBee, NFC, or the like, or any combination thereof. Two or more modules may be combined into a single module, and any one module may be divided into two or more units.

An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program performs the steps of the service location obtaining method according to any of the above embodiments.

To sum up, according to the service order payment method, device, electronic device, and storage medium provided by the embodiments of the present application, the first operation button is displayed when the service order is completed, the service provider responds to the operation of the first operation button, receives the unique digital object identifier associated with the service order sent by the server, and displays the unique digital object identifier, where the unique digital object identifier is used to identify a payment link of the service order. The unique identifier of the digital object sent by the server can be automatically acquired through the operation of the first operation button by the service provider, compared with a code scanning payment mode in the prior art, the operation process is simplified, the operation experience of the service provider is improved, and the waiting cost of the service requester is reduced; because the digital object unique identifier is associated with the service order, after the service requester pays for the service order according to the digital object unique identifier, the server can obtain the payment details of the service order, and once payment disputes occur subsequently, the server is well documented.

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

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

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

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

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

Claims

1. A service order payment method, the method comprising:

displaying a first operation button when the service order is completed; the payment mode corresponding to the first operation button is code scanning payment;

receiving a digital object unique identifier associated with the service order generated and transmitted by a server in response to an operation of the first operation button by a service provider;

displaying the digital object unique identifier, wherein the digital object unique identifier is used for identifying a payment link of the service order, so that a service requester can pay for the service order according to the digital object unique identifier displayed on the service provider terminal;

displaying a service ending page corresponding to the processing process according to the different processing processes of the service order by the service requester based on the unique identifier of the digital object; wherein the step of displaying a service end page corresponding to the processing process for different processing processes of the service order based on the unique identifier of the digital object according to the service requester comprises: when the processing process represents that the service requester does not confirm payment amount, displaying a first service ending page, wherein the first service ending page comprises a first payment state and a payment mode of the service requester; wherein the unconfirmed payment amount of the service requester means that the service requester does not scan the unique identifier of the digital object, or does not input the payment amount after scanning the unique identifier of the digital object, or does not confirm the payment after scanning the unique identifier of the digital object and inputting the payment amount;

and displaying a second operation button on the first service ending page, wherein the payment mode corresponding to the second operation button is different from the code scanning payment.

2. The method of claim 1, wherein the step of displaying a first operating button upon completion of the service order comprises:

3. The method of claim 1, wherein the step of displaying a service end page corresponding to the processing procedure according to the different processing procedure of the service requester for the service order based on the digital object unique identifier comprises:

4. The method of claim 3, further comprising:

5. The method of claim 1, wherein the step of displaying a service end page corresponding to the processing procedure according to the different processing procedure of the service requester for the service order based on the digital object unique identifier comprises:

6. The method of claim 1, wherein the step of displaying a first operating button upon completion of the service order comprises: when the service order is completed, displaying the first operating button and the second operating button;

the method further comprises the following steps:

7. The method of claim 1, wherein the step of displaying the unique identifier of the digital object comprises:

displaying the digital object unique identifier in a floating layer manner.

8. The method of any of claims 1-7, wherein the digital object unique identifier comprises an order number, an order type, time information, identification information of the service provider, and identification information of the service requester corresponding to the service order.

9. The method of any of claims 1-7, wherein the digital object unique identifier is a two-dimensional code or a bar code.

10. A service order payment method, the method comprising:

generating a digital object unique identifier associated with a service order when payment means confirmation information transmitted by a service provider terminal in response to an operation of a first operation button by a service provider is received, wherein the first operation button is displayed on the service provider terminal when the service order is completed; the payment mode corresponding to the first operation button is code scanning payment;

transmitting the digital object unique identifier to the service provider terminal, wherein the digital object unique identifier displayed on the service provider terminal is used to identify a payment link for the service order for a service requester to pay for the service order according to the digital object unique identifier displayed on the service provider terminal;

when process information sent by a service requester terminal according to different processing processes of the service order by the service requester based on the unique identifier of the digital object is received, sending service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing processes; wherein, when receiving process information sent by a service requester terminal according to different processing processes of the service order by the service requester based on the unique identifier of the digital object, the step of sending service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing processes includes: when the process information represents that the service requester does not confirm payment amount, sending first service end page display information to the service provider terminal to control the service provider terminal to display a first service end page corresponding to the processing process, wherein the first service end page comprises a first payment state and a payment mode of the service requester; wherein the unconfirmed payment amount of the service requester means that the service requester does not scan the unique identifier of the digital object, or does not input the payment amount after scanning the unique identifier of the digital object, or does not confirm the payment after scanning the unique identifier of the digital object and inputting the payment amount;

and sending operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the first service ending page, wherein the payment mode corresponding to the second operation button is different from the code scanning payment.

11. The method of claim 10, wherein the step of generating a unique identifier for the digital object associated with the service order comprises:

12. The method of claim 10, further comprising:

13. The method according to claim 10, wherein the step of transmitting service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing progress, when receiving progress information transmitted by a service requester terminal according to different processing progresses of the service order by a service requester based on the digital object unique identifier, comprises:

14. The method of claim 13, further comprising:

15. The method according to claim 10, wherein the step of transmitting service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing progress, when receiving progress information transmitted by a service requester terminal according to different processing progresses of the service order by a service requester based on the digital object unique identifier, comprises:

16. The method of claim 10, further comprising:

17. The method of any of claims 10-16, wherein the digital object unique identifier is a two-dimensional code or a bar code.

18. A service order payment apparatus, the apparatus comprising:

the first display module is used for displaying a first operation button when the service order is completed; the payment mode corresponding to the first operation button is code scanning payment;

the receiving module is used for responding to the operation of the service provider on the first operation button and receiving the unique identifier of the digital object which is generated and sent by the server and is associated with the service order;

a second display module, configured to display the unique digital object identifier, where the unique digital object identifier is used to identify a payment link of the service order, so that a service requester pays for the service order according to the unique digital object identifier displayed on a service provider terminal;

the third display module is used for displaying a service ending page corresponding to the processing process according to different processing processes of the service order by the service requester based on the unique identifier of the digital object; the third display module is configured to display a first service end page when the processing process represents that the service requester does not confirm the payment amount, where the first service end page includes a first payment status and a payment mode of the service requester; wherein the unconfirmed payment amount of the service requester means that the service requester does not scan the unique identifier of the digital object, or does not input the payment amount after scanning the unique identifier of the digital object, or does not confirm the payment after scanning the unique identifier of the digital object and inputting the payment amount;

the first display module is further used for displaying a second operation button on the first service end page, and a payment mode corresponding to the second operation button is different from a code scanning payment mode.

19. The apparatus of claim 18, wherein the first display module is configured to display the first button in response to a confirmation operation by the service provider of completion of the service order.

20. The apparatus of claim 18, wherein the third display module is configured to display a second end-of-service page when the processing procedure characterizes that the service requestor has confirmed a payment amount and has not completed payment; wherein the second service end page includes a second payment status, a payment amount, and a payment method of the service requester.

21. The apparatus of claim 20, wherein the first display module is further configured to display a second operation button on the second service end page, and wherein a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

22. The apparatus of claim 18, wherein the third display module is configured to display a third end-of-service page when the processing procedure characterizes that the service requestor has confirmed a payment amount and completed a payment; wherein the third service end page includes a third payment status, a payment amount, and a payment method of the service requester.

23. The apparatus of claim 18, wherein the first display module is configured to display the first and second operating buttons upon completion of a service order;

the device further comprises:

24. The apparatus of claim 18, wherein the second display module is configured to display the unique identifier of the digital object in a floating layer.

25. The apparatus of any of claims 18-24, wherein the digital object unique identifier comprises an order number, an order type, time information, identification information of the service provider, and identification information of the service requester corresponding to the service order.

26. The apparatus of any one of claims 18-24, wherein the unique identifier of the digital object is a two-dimensional code or a bar code.

27. A service order payment apparatus, the apparatus comprising:

an identifier generating module, configured to generate a digital object unique identifier associated with a service order when payment means confirmation information transmitted by a service provider terminal in response to an operation of a first operation button by a service provider is received, wherein the first operation button is displayed on the service provider terminal when the service order is completed; the payment mode corresponding to the first operation button is code scanning payment;

a first sending module, configured to send the unique digital object identifier to the service provider terminal, where the unique digital object identifier displayed on the service provider terminal is used to identify a payment link of the service order, so that a service requester pays for the service order according to the unique digital object identifier displayed on the service provider terminal;

a third sending module, configured to, when receiving process information sent by a service requester terminal according to a different processing process of the service order by the service requester based on the unique digital object identifier, send service end page display information to the service provider terminal to control the service provider terminal to display a service end page corresponding to the processing process; the third sending module is configured to send, when the process information represents that the service requester does not confirm the payment amount, first service end page display information to the service provider terminal to control the service provider terminal to display a first service end page corresponding to the processing process, where the first service end page includes a first payment status and a payment mode of the service requester; wherein the unconfirmed payment amount of the service requester means that the service requester does not scan the unique identifier of the digital object, or does not input the payment amount after scanning the unique identifier of the digital object, or does not confirm the payment after scanning the unique identifier of the digital object and inputting the payment amount;

and the second sending module is used for sending operation button display information to the service provider terminal so as to control the service provider terminal to display a second operation button on the first service ending page, wherein a payment mode corresponding to the second operation button is different from code scanning payment.

28. The apparatus of claim 27, wherein the identifier generating module is configured to generate the unique identifier of the digital object according to an order number, an order type, time information, identification information of the service provider, and identification information of the service requester corresponding to the service order.

29. The apparatus according to claim 27, wherein the second sending module is further configured to send operation button display information to the service provider terminal to control the service provider terminal to display the first operation button when receiving confirmation operation information sent by the service provider terminal in response to a confirmation operation of the service provider for completion of the service order.

30. The apparatus of claim 27, wherein the third sending module is configured to send second service end page display information to the service provider terminal to control the service provider terminal to display a second service end page corresponding to the processing procedure when the procedure information represents that the service requester has confirmed a payment amount and does not complete payment; wherein the second service end page includes a second payment status, a payment amount, and a payment method of the service requester.

31. The apparatus of claim 30, wherein the second sending module is further configured to send operation button display information to the service provider terminal to control the service provider terminal to display a second operation button on the second service end page, wherein a payment method corresponding to the first operation button is different from a payment method corresponding to the second operation button.

32. The apparatus of claim 27, wherein the third sending module is configured to send third service end page display information to the service provider terminal to control the service provider terminal to display a third service end page corresponding to the processing procedure when the progress information represents that the service requester has confirmed the payment amount and completed the payment; wherein the third service end page includes a third payment status, a payment amount, and a payment method of the service requester.

33. The apparatus of claim 27, wherein the second sending module is further configured to send operation button display information to the service provider terminal to control the service provider terminal to display the first operation button in a floating manner when receiving a payment method change request sent by the service provider terminal, wherein the payment method change request is generated when the service provider selects to change a payment method corresponding to the second operation button displayed on the service provider terminal to another payment method.

34. The apparatus of any one of claims 27-33, wherein the unique identifier for the digital object is a two-dimensional code or a bar code.

35. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is run, the processor executing the machine-readable instructions to perform the steps of the service order payment method according to any one of claims 1 to 9 when executed.

36. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the service order payment method according to any one of claims 1 to 9.

37. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the electronic device is run, the processor executing the machine-readable instructions to perform the steps of the service order payment method according to any one of claims 10 to 17 when executed.

38. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the service order payment method according to any one of claims 10 to 17.