CN108389268B

CN108389268B - Payment method, system and equipment

Info

Publication number: CN108389268B
Application number: CN201810123030.XA
Authority: CN
Inventors: 史春利; 舒成兵; 王鹤
Original assignee: Zhejiang Lianhe Technology Co ltd
Current assignee: Zhejiang Lianhe Technology Co ltd
Priority date: 2018-02-07
Filing date: 2018-02-07
Publication date: 2021-10-19
Anticipated expiration: 2038-02-07
Also published as: CN108389268A

Abstract

The embodiment of the application provides a payment method, a payment system and payment equipment. The payment method comprises the following steps: acquiring a first service party for charging a charging object; when the first service party is one of at least one first service party associated with a second service party, obtaining exemption data generated by a user applying for paying for the charging object at the second service party; and determining payment data which the user needs to pay to the first service party according to the exemption data and the total charging amount generated by the charging object. The technical scheme provided by the embodiment of the application provides a charging exemption mutual-recognition scheme among a plurality of independent service parties, and solves the problem that two, three or more independent service parties cannot get through due to high integration difficulty of a charging system in the prior art; not only provides convenience for each service party, but also provides more convenience for users of each service party, and is beneficial to improving the service quality of each service party.

Description

Payment method, system and equipment

Technical Field

The present application relates to the field of network technologies, and in particular, to a payment method, system, and device.

Background

When a user parks in a parking lot of a service provider (such as a shopping mall, a catering business and the like) with a parking lot, the user can mostly enjoy parking benefits given by the service provider, such as membership exemption, shopping exemption, point exemption and the like. Therefore, the user prefers to go to such a service provider with a free parking lot for consumption.

For the service provider without own parking lot, there are more problems, such as payment and settlement mode, system communication, cooperation management, etc., due to cooperation with the external parking lot; so that most of the existing service providers without own parking lots cannot give corresponding parking benefits to users.

Disclosure of Invention

In view of the above, the present application is directed to a payment method, system and device that solves, or at least partially solves, the above problems.

Thus, in one embodiment of the present application, a payment method is provided. The method comprises the following steps:

acquiring a first service party for charging a charging object;

when the first service party is one of at least one first service party associated with a second service party, obtaining exemption data generated by a user applying for paying for the charging object at the second service party;

and determining payment data which the user needs to pay to the first service party according to the exemption data and the total charging amount generated by the charging object.

In another embodiment of the present application, a payment method is provided. The method comprises the following steps:

receiving a payment request sent by a client, wherein the payment request carries a charging object, a first service party for charging the charging object and payment data;

executing payment operation of paying the payment data to the first service party aiming at the charging object;

the payment data is determined according to exemption data and the total charging amount generated by the charging object at the first service party; the exemption data is obtained from the second service party when the first service mode is one of at least one first service party associated with the second service party, and is generated at the second service party by a user applying for paying for the charging object.

In yet another embodiment of the present application, a payment method is provided. The method comprises the following steps:

charging the charging object to obtain the total charging amount generated by the charging object;

receiving prompt information sent by the server after payment data is executed by the server aiming at the charging object;

outputting the prompt information;

the payment data is determined according to the deduction data and the total charging amount; the exemption data is acquired from a second service party when a first service mode for charging the charging object is one of at least one first service party associated with the second service party, and is generated at the second service party by a user applying for paying for the charging object.

In one embodiment of the present application, a payment system is provided. This payment system includes:

the client is used for acquiring a first service party for charging the charging object; when the first service party is one of at least one first service party associated with a second service party, obtaining exemption data generated by a user applying for paying for the charging object at the second service party; determining payment data which the user needs to pay to the first service party according to the exemption data and the total charging amount generated by the charging object;

the server is used for receiving a payment request sent by the client, wherein the payment request carries the charging object, the first server and the payment data; executing payment operation of paying the payment data to the first service party aiming at the charging object;

the first service party is used for charging the incoming charging object to obtain the total charging amount generated by the charging object; receiving prompt information sent by the server after the server executes payment data for the charging object; and outputting the prompt information.

responding to a payment event triggered by a user through a corresponding interface of a second service party, and displaying a page element corresponding to the charging object in the payment interface;

when the first service party charging the charging object is one of at least one first service party associated with the second service party, displaying the exemption data generated by the user at the second service party in the payment interface;

and displaying payment data which is determined according to the deduction data and the total charging amount generated by the charging object and is required to be paid to the first service party by the user.

In one embodiment of the present application, a client device is provided. The client device includes: a first memory and a first processor, wherein,

the first memory is used for storing programs;

the first processor, coupled with the first memory, to execute the program stored in the first memory to:

acquiring a first service party for charging a charging object;

In one embodiment of the present application, a server device is provided. The server device includes: a second memory and a second processor, wherein,

the second memory is used for storing programs;

the second processor, coupled to the second memory, is configured to execute the program stored in the second memory to:

In one embodiment of the present application, a first server device is provided. The first server device includes: a third memory and a third processor, wherein,

the third memory is used for storing programs;

the third processor, coupled to the third memory, is configured to execute the program stored in the third memory to:

outputting the prompt information;

The technical scheme provided by the embodiment of the application provides a charging deduction and mutual recognition scheme among a plurality of independent service parties, namely the total charging amount generated by a binding charging object of a user at a first service party can be subjected to preferential deduction by the deduction data generated by the user at a second service party, and the problem that two, three or more independent service parties cannot get through due to high integration difficulty of a charging system in the prior art is solved; not only provides convenience for each service party, but also provides more convenience for users of each service party, and is beneficial to improving the service quality of each service party.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic structural diagram of a payment system according to an embodiment of the present application;

fig. 2 is a schematic flow chart of a payment method according to an embodiment of the present application;

fig. 3 is a diagram illustrating an implementation example of a payment interface according to an embodiment of the present application;

FIG. 4 is a diagram of an implementation example of a payment order detail interface according to another embodiment of the present application;

fig. 5 is a schematic flow chart of a payment method according to another embodiment of the present application;

fig. 6 is a schematic flow chart of a payment method according to another embodiment of the present application;

fig. 7 is a schematic flow chart of a payment method according to another embodiment of the present application;

fig. 8 is a schematic structural diagram of a payment device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a payment device according to another embodiment of the present application;

fig. 10 is a schematic structural diagram of a payment device according to another embodiment of the present application;

fig. 11 is a schematic structural diagram of a payment device according to another embodiment of the present application;

fig. 12 is a schematic structural diagram of a client device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a server device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a first server device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the prior art, the operation of the two service parties is independent from the operation of the independent parking lot and the operation of the shopping mall without the own parking lot. The user's parking fee generated in the parking lot cannot enjoy the similar benefits given by the mall having the own parking lot, such as mall membership exemption, shopping exemption, point exemption, and the like. To solve the problem, the application provides a solution, and the main idea is as follows: the method comprises the steps that a common service platform is provided for a plurality of service parties, a first service party and a second service party can establish an association relation on the service platform based on a cooperation agreement, and when a user consumes two service parties with the association relation, consumption generated at one service party can enjoy the benefit given by the other service party. Wherein, the preferential rule can be defined by the preferential service provider.

The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Before introducing the service providing method provided by the present application, a system architecture on which the method provided by the present application is based is explained.

As shown in fig. 1, a schematic structural diagram of a payment system provided in an embodiment of the present application is shown. As shown in fig. 1, the system provided in this embodiment includes: a client 101, a server 102 and a first server 103. Wherein the content of the first and second substances,

a client 101, configured to obtain a first service party 103 that charges a charging object; when the first service party 103 is one of at least one first service party associated with a second service party, obtaining exemption data generated by a user applying for paying for the charging object at the second service party; determining payment data which the user needs to pay to the first service party 103 according to the exemption data and the total charging amount generated by the charging object;

the server 102 is configured to receive a payment request sent by the client 101, where the payment request carries the charging object, the first server 103, and the payment data; for the charging object, executing a payment operation of paying the payment data to the first service party 103;

the first service party 103 is configured to charge the charging object to obtain a total charging amount generated by the charging object; receiving prompt information sent by the server after the server executes payment data for the charging object; and outputting the prompt information.

Here, it should be noted that: the system provided by the embodiment can be applied to application scenes of cooperation of various service parties, for example, application scenes of cooperation of parking lots and shopping malls. If the charging object bound with the user in the embodiment can be a vehicle in an application scene of cooperation of a parking lot and a shopping mall; the total amount is charged, namely the parking fee; the first service party is a parking lot operator providing parking service for the vehicle; the second service party is an on-premise facilitator that provides off-line and/or on-line consumption services for the user. In particular implementations, the exemption data may be determined based on whether the user is a member (i.e., a registered user), the consumption credits of the user at the mall, the consumption amount of the user at the mall, and the like.

In addition, the specific workflow of each component unit, such as the client, the server, and the first service side, and the signaling interaction between the component units in the payment system provided in the embodiment of the present application will be further described in the following embodiments.

Fig. 2 shows a schematic flow chart of a payment method according to an embodiment of the present application. The method provided by the embodiment is suitable for the client. The client may be a hardware integrated on the terminal and having an embedded program, may also be an application software installed in the terminal, and may also be a tool software embedded in an operating system of the terminal, which is not limited in this embodiment of the present invention. The terminal may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, and the like. As shown in fig. 2, the payment method includes:

201. and acquiring a first service party for charging the charging object.

202. And when the first service party is one of at least one first service party associated with a second service party, acquiring the exemption data generated by the user applying for paying for the charging object at the second service party.

203. And determining payment data which the user needs to pay to the first service party according to the exemption data and the total charging amount generated by the charging object.

In the above 201, the charging object may be input by the user through a user interface (such as the payment interface shown in fig. 3), or may be obtained by the client from binding information preset by the user. In a feasible technical scheme, a user can bind user information (such as login information) of the user with an identifier of a charging object in advance through a binding function provided by a client. The binding information may be stored locally at the client or uploaded to the server, which is not limited in this embodiment of the present invention. Of course, in the implementation, the charging object bound to the user may be one or more. When a plurality of bound charging objects are available, the client may obtain a plurality of charging objects according to the user information of the login application, and select one of the charging objects to be displayed on a user interface (e.g., the payment interface shown in fig. 3). If the displayed charging object is not the charging object for which the user wants to pay, the user can trigger and display at least one other charging object by touching a selection control key on the user interface, such as a V-shaped control key displayed beside the license plate number in fig. 3, and the user can select the charging object for which the user wants to pay to the first service party.

In addition, in the above 201, the first service party may be obtained by the client from the service end, or may be obtained by scanning a code by the user. That is, the obtaining manner of the first service party in this step 201 may include:

acquiring the first service party from a service end; or

Determining the first server based on the scanned code.

The precondition for acquiring the first service party from the service end is that the service end stores the charging information of the charging object. The charging information at least comprises a charging object and a first service party for charging the charging object. The charging information may be uploaded to the service by the first service party when the charging of the charging object is started. For example, in a practical implementation, when the user inputs the charging object through the payment interface shown in fig. 3, the client may send an acquisition request carrying the charging object to the server; after receiving the acquisition request, the server searches for a first service party corresponding to a charging object pointed by the acquisition request by inquiring the charging information, and then feeds back the inquired first service party to the client. Or after receiving the charging information of the charging object uploaded by the first service party, the service side synchronizes the charging object to the client side; in fact, the server can synchronize to all clients, or synchronize only to the client corresponding to the user bound to the charging object; therefore, the client can search the first service party corresponding to the charging object which the user wants to pay locally.

The scanned codes can be obtained by scanning payment two-dimensional codes placed in a parking lot or payment two-dimensional codes provided by parking lot staff by a user.

Here, it should be noted that: the payment interface may be triggered and displayed after the user clicks a payment control key on the application interface, may also be triggered and displayed after the user performs a shake operation, may also be triggered and displayed after the user sends a designated voice (such as a "parking payment" voice), may also be triggered and displayed after scanning a payment two-dimensional code of a code parking lot, and the like.

In 202, the association relationship between the second service party and the at least one first service party is configured in advance. The association between the second service party and the at least one first service party may be maintained by a service end (i.e. a service platform). For example, a service-side worker may establish an association relationship and a cooperation rule for two independent service parties at the service side based on a cooperation agreement between the two independent service parties offline. The purpose of establishing the association relationship is to facilitate the judgment of whether the consumption of the user on the first service party can be preferential by a preferential strategy provided by the second service party or not; the collaboration rules are for revenue settlement of the two subsequent independent service parties. Here, it should be noted that: the cooperation rule between two independent service parties is not the key point of the technical scheme, and the cooperation rule is determined by the two independent service parties through offline negotiation.

In particular, the association relationship between the second service party and the at least one first service party can also be synchronized to the client. Thus, the client can directly inquire the locally stored association information, and can judge whether the first service party is one of at least one first service party associated with the second service party.

When the first service party is associated with the second service party, the exemption data generated by the user at the second service party can be obtained by the following method:

2021. when the user is a registered user of the second service party, the registered exclusive share data provided by the second service party to the registered user is used as the exemption data; and/or

2022. Acquiring offline consumption data generated by the user at the second service party, and converting the offline consumption data into exemption data; and/or

2023. And acquiring accumulated data generated at the second server in the user history period, and converting the accumulated data into the exemption data.

The conversion rule for converting the consumption data into the exemption data and the conversion rule for converting the accumulated data into the exemption data can be defined by the second service party. The conversion rule self-defined by the second service party can be maintained by the service side and synchronized to the client side; and the client converts the offline consumption data or the accumulated data uploaded to the client by the user according to the locally stored conversion rule to obtain the exemption data.

The offline consumption data can be obtained in one of the following two ways:

in the first mode, offline consumption data consumed by the user at the second service party is obtained by scanning codes (such as two-dimensional codes) on consumption tickets consumed by the user at the second service party.

And secondly, acquiring offline consumption data consumed by the user at the second service party by shooting the consumption tickets consumed by the user at the second service party.

That is, the above-mentioned obtaining the offline consumption data generated by the user at the second service provider may specifically include:

in response to a user-triggered code scanning event, determining the offline consumption data based on code scanning information; or

In response to a user-triggered capture event, the offline consumption data is determined based on the captured picture.

What needs to be added here is: in practical applications, the number of uses of the scanned or photographed consumption ticket by the user should be limited, such as the scanned or photographed consumption ticket cannot be converted into the exempt data. For this reason, the method provided in this embodiment may further include the following steps:

and uploading the offline consumption data of the converted exemption data to a server, wherein the offline consumption data at least comprises offline consumption amount and identification.

Correspondingly, the step "2022, obtaining offline consumption data generated by the user at the second service provider, and converting the offline consumption data into the exemption data" specifically includes:

acquiring offline consumption data generated by the user at the second server, sending the offline consumption data to the server, and judging whether the offline consumption data is converted data or not by the server according to an identifier contained in the offline consumption data;

if a negative response fed back by the server is received, converting the offline consumption data into the exemption data;

and if a confirmation response fed back by the server side is received, outputting a prompt message that the offline consumption data is used.

In specific implementation, the prompt information can be output by adopting modes such as voice playing, interface display and the like.

The exemption data 203 may be an exemption value or an exemption rate (e.g., discount). Correspondingly, the payment data is determined in the following manner:

subtracting the exemption data from the total charging amount to obtain the payment data; or

And multiplying the total charging amount by the exemption data to obtain the payment data.

Here, it should be noted that: the total charging amount generated by the charging object can be input into the client by the user, or can be acquired by the client from the first service party. In practical application, a user can inquire the staff in the parking lot and input the numerical value to the client according to the numerical value informed by the staff. Or, the client sends an obtaining request for obtaining the total charging amount of the charging object to the server, the server queries a first server for charging the charging object, then obtains the total charging amount of the charging object generated at the first server from the first server, and feeds back the total charging amount to the client.

Further, the payment method provided in this embodiment may further include:

204. and responding to a confirmation event triggered by the user aiming at the payment data, sending a payment request to a server so that the server carries out the operation of paying the payment data to the first service party aiming at the charging object.

The server performs the operation of paying the payment data to the first server party for the charging object, which may refer to the existing network payment technology and is not described herein again.

Further, the payment method provided in this embodiment may further include:

205. and acquiring historical behavior data of the user.

206. And determining recommendation information for the user according to the historical behavior data.

207. And after the user successfully pays the payment data for the first service, outputting the recommendation information.

The historical behavior data in 205 may be a historical consumption record of the user (e.g., a consumption amount of a certain shop for offline consumption uploaded by the user through the client application), a historical review record (e.g., a certain category of goods frequently reviewed by the user through the client application), a historical browsing record (e.g., a certain shop browsed through the client application), a historical operation record (e.g., information about collected goods), and so on. The obtaining mode of the historical behavior data may specifically include: acquiring an internet surfing record of a user through a gateway; and/or acquiring a behavior log stream of the user from the application platform; and/or based on a data cookie stored on the user's local terminal, etc., which are not specifically limited in this embodiment of the present application.

In 206, determining recommendation information for the user according to the historical behavior data may specifically include the following steps:

calculating the portrait characteristics of the user according to the historical behavior data of the user, and determining first recommended content for the user according to the portrait characteristics; and/or

Searching similar users similar to the user according to the historical behavior data of the user, and determining second recommended content for the user according to the similar users; and/or

Acquiring third recommended content associated with the behavior object according to the behavior object in the historical behavior data of the user;

wherein the recommendation information includes: the first recommended content, the second recommended content, and/or the third recommended content.

In particular, the portrait characteristics of the user may be a set of tags characterizing the user. For example, the portrait characteristics may include basic attributes such as age, gender, and region, and may also include interest characteristics, preferences, and the like of the user. In an application example of the present invention, it is assumed that obtaining portrait characteristics of a user by using historical behavior data of the user specifically includes: for a woman, the age of 24 years, the preference for Sichuan dishes in catering, the preference for popular fashion brands in clothing category, and the like, the recommended contents for the user according to the portrait characteristics are as follows: coupons from the restaurant, coupons from the popular tide brand, and so on.

The similar users similar to the user may be users having the same interests as the current user, and specifically, the similar users of the current user may be calculated by a user based (user based) algorithm. The specific process can be as follows: calculating interest characteristics of the user according to historical behavior data of the user, wherein the interest characteristics may include operation characteristics of the user on a historical behavior object (a certain merchant or a certain specific product), such as: searching, browsing, paying attention, collecting, consuming and the like, establishing an interest feature vector of the user by taking the interest feature as a dimension, calculating the similarity between other users and the current user by utilizing the interest feature vector, determining the user with the similarity larger than a first threshold value as the similar user of the current user, and determining second recommended content recommended by the user according to the recommended content of the similar user.

The behavior objects of the historical behavior data of the user may be: merchants, products, and the like. For example, in a specific application example, assuming that a user consumes at a restaurant, behavior objects of the historical behavior data of the user are: a Sichuan restaurant; assuming that the user collects the commodity, the behavior object of the historical behavior data of the user is: commercial product. Based on the behavior object, content associated with the behavior object may be treated as recommended content. Similarly, when the behavior object in the historical behavior data of the user is the product, the discount message of the product may be used as the recommended content, or the coupon of the product similar to the product may be used as the recommended content, and so on. For example, recommendation information of "× 10-element voucher" is displayed at the lowermost part of the user interface (i.e., the payment order detail interface) as shown in fig. 4.

Here, it should be noted that: the method provided by the embodiment can be applied to application scenes of cooperation of various service parties, for example, application scenes of cooperation of parking lots and shopping malls. If the charging object bound with the user in the embodiment can be a vehicle in an application scene of cooperation of a parking lot and a shopping mall; the total amount is charged, namely the parking fee; the first service party is a parking lot operator providing parking service for the vehicle; the second service party is an on-line service provider for providing off-line and/or on-line consumption services for the user; the exemption data may be determined based on whether the user is a member (i.e., a registered user), the consumption points of the user at the mall, the consumption amount of the user at the mall, and the like.

Fig. 5 shows a schematic flow chart of a payment method according to another embodiment of the present application. The method provided by the embodiment is suitable for the server. The server may be a common server, a cloud, a virtual server, and the like, which is not specifically limited in this embodiment of the application. As shown in fig. 5, the method provided by this embodiment includes:

301. receiving a payment request sent by a client, wherein the payment request carries a charging object, a first service party for charging the charging object and payment data.

302. And executing payment operation of paying the payment data to the first service party aiming at the charging object.

Specifically, the exemption data may be determined by the client (see the relevant contents in the above embodiments, which are not described herein), or may be determined by the server and synchronized to the client. After the user executes the confirmation operation on the payment data displayed in the client, the client sends the payment request to the server. For example, after the user clicks the "6 payment confirmation" control key shown in fig. 3, the client sends the payment request to the server.

Based on the above embodiments, the exempt data may be derived from the registration-specific data, and/or may be converted from offline consumption data generated by the user at the second service, and/or may be converted from cumulative data generated by the user at the second service during a historical period, and so on. And the rules for converting the offline consumption data and the accumulated data corresponding to each second service party into the exemption data can be stored in the service end. The client can send the acquired offline consumption data or accumulated data to the server; and the server converts the received offline consumption data or the accumulated data based on a rule corresponding to a locally stored second server for offline consumption or a second server for user accumulated data, and sends the converted exemption data to the client.

In addition, for the offline consumption data of the converted exempt data mentioned in the above embodiment, the server maintains a list in which the identification of the offline consumption data that has been converted is stored. After receiving offline consumption data sent by a client, a server inquires whether the list contains an identifier of the offline consumption data; if yes, representing that the offline consumption data are converted data; otherwise, the offline consumption data is represented as unconverted data. The server side feeds back a judgment result to the client side; when the client receives a judgment result fed back by the server and the offline consumption data are unconverted data, converting the offline consumption data into exemption data according to a locally stored rule corresponding to a second server; and when the client receives the judgment result fed back by the server that the offline consumption data is converted data, outputting the used prompt information of the offline consumption data. Or when the server judges that the offline consumption data are unconverted data, converting the offline consumption data into exemption data according to a rule corresponding to a second server, and feeding back the exemption data to the client; and the server side feeds back a used prompt response of the offline consumption data to the client side after judging that the offline consumption data are converted data, so that the client side outputs used prompt information of the offline consumption data.

In 302, the server performs the operation of paying the payment data to the first server party for the charging object, which refers to the existing network payment technology and is not described herein again.

Further, the method provided by the above embodiment further includes:

303. and receiving and storing the charging information of the charging object uploaded by at least one first service party.

304. And feeding back a first service party which charges the charging object pointed by the acquisition request to the client side sending the acquisition request by inquiring the charging information.

Further, the method provided by the above embodiment further includes:

305. and acquiring historical behavior data of the user applying for paying for the charging object.

306. And determining recommendation information for the user according to the historical behavior data.

307. And after the payment operation is successful, sending the recommendation information to the client.

Specifically, the above 306 can be implemented by the following method:

Here, it should be noted that: in the embodiment, the historical behavior data about the user, how to determine recommendation information for the user based on the historical behavior data, and the like can be referred to the relevant contents in the above embodiments, and details are not described here.

Here, it should be noted that: the payment method provided by the embodiment can be applied to various application scenes, such as application scenes of cooperation of a parking lot and a shopping mall. If the method provided by the embodiment is applied to an application scene of cooperation of a parking lot and a shopping mall, the charging object is a vehicle; the first service party (i.e. parking lot) provides parking service for the vehicle; the second service party (i.e., the mall) provides offline and/or online services for the user.

Fig. 6 shows a schematic flow chart of a payment method according to another embodiment of the present application. The method provided by this embodiment is applicable to a first service party, where the first service party may be a hardware integrated on a terminal and having an embedded program, may also be an application software installed in the terminal, and may also be a tool software embedded in an operating system of the terminal, and the like. The terminal may be any terminal device including a mobile phone, a desktop computer, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, and the like. Specifically, as shown in fig. 6, the method provided in this embodiment includes:

401. and charging the charging object to obtain the total charging amount generated by the charging object.

402. And receiving prompt information sent by the server after the payment data is executed by the server aiming at the charging object.

403. And outputting the prompt information.

In the above 401, the charging rule for the charging object may be defined by the first service party. For example, a time-based charging rule; the first service party can calculate the total charging amount generated by the charging object from the entrance moment to the user application exit moment based on the preset time charging rule.

In 402, if the server executes successfully, the prompt message may be that the payment is successful; if the execution of the server fails, the prompt message may be a payment failure.

The output mode of the prompt message in 403 may be: speech output, text message output, etc.

The exemption data in this embodiment may be determined by the client or the server, and specific implementation may refer to relevant contents in the above embodiments, which is not described herein again.

The technical scheme provided by the embodiment of the application provides a charging deduction and mutual recognition scheme among a plurality of independent service parties, namely the service data generated by a binding charging object of a user at a first service party can be used for carrying out preferential deduction on the total charging amount by the deduction data generated by the user at a second service party so as to obtain the payment data which needs to be paid to the first service party by the user, and the problem that two, three or more independent service parties cannot get through due to high integration difficulty of a charging system in the prior art is solved.

Here, it should be noted that: the payment method provided by the embodiment can be applied to various application scenes, such as application scenes of cooperation of a parking lot and a shopping mall. If the method provided by the embodiment is applied to an application scene of cooperation of a parking lot and a shopping mall, the charging object is a vehicle; the server is a service platform for providing solutions for the first service party and the second service party; the first service party (i.e. parking lot) provides parking service for the vehicle; the second service party (i.e., the mall) provides offline and/or online services for the user.

In an application scenario where the parking lot and the shopping mall cooperate, the method provided by this embodiment may further include:

403. and when the entering of a charging object is monitored, charging information corresponding to the charging object is sent to a server so as to be stored in the server.

The purpose of the server storing the charging information of the charging object is to obtain the server corresponding to the charging object requested by the client by inquiring the charging information of a plurality of locally stored charging objects when the server corresponding to a certain charging object is subsequently received and the client requests to obtain the server corresponding to the charging object, and then feed back the required server information.

In practical application, monitoring equipment (such as a camera) can be used for monitoring whether a charging object enters the field or not; and after shooting the entrance of the charging object, the monitoring equipment sends the entrance information to the first service party. And after receiving the near field information, the first service party characterizes that the first service party monitors that the charging object enters the field. Wherein, the first service party can be simply understood as: an upper computer in the parking lot management system; the monitoring equipment is a camera or card taking equipment arranged at the entrance of the parking lot.

Fig. 7 shows a schematic flow chart of a payment method according to another embodiment of the present application. As shown in fig. 7, the method provided by this embodiment is suitable for the client. The client may be a hardware integrated on the terminal and having an embedded program, may also be an application software installed in the terminal, and may also be a tool software embedded in the terminal operating system, which is not limited in this embodiment of the present invention. The terminal may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, and the like. Here, it should be noted that: the embodiment shown in fig. 2 above describes the method provided by the embodiment from the front-end implementation perspective of the client; the method provided by the embodiment will be described in conjunction with the interface and the front end of the client. As shown in fig. 7, the payment method includes:

501. and responding to a payment event triggered by the user through the interface corresponding to the second service party, and displaying a page element corresponding to the charging object in the payment interface.

502. And when the first service party which charges the charging object is one of at least one first service party associated with the second service party, displaying the exemption data generated by the user at the second service party in the payment interface.

503. And displaying payment data which is determined according to the deduction data and the total charging amount generated by the charging object and is required to be paid to the first service party by the user.

Fig. 3 shows an implementation form of the payment interface, and the payment interface may also take other implementation forms, which is not limited in this embodiment.

In 501, the payment event may be triggered after the user sends the corresponding voice password, triggered after the user touches a control key on the client interface, triggered after the user performs a shake action, or the like, which is not limited in the embodiments of the present invention. That is, the method provided in this embodiment further includes:

when monitoring that the user performs the specified action, triggering the payment event; or

When monitoring that a user sends out a designated voice, triggering the payment event; or

And triggering the payment event when the touch operation of the user on the appointed control key is monitored.

Wherein, the designated action can be shaking, turning and other actions; the designated voice can be a preset voice password; the designated control key can be a scanning control key or a parking payment control key on the client interface.

The present embodiment provides an implementation that each second server has a corresponding page on the client side. The user can enter the page of the second service party to view all the service information provided by the second service party. Assuming that the second service party is a market, after the client enters a page corresponding to the market, the user can check an indoor map of the market, search for a storefront, pay parking fees, queue a collar number, select a seat for a movie, and the like. When a user triggers a payment event for paying for a charging object through a corresponding interface of a second service party, a client needs to judge whether the second service party has a relationship with a first service party corresponding to the charging object in advance; having an association, the client displays the exemption data generated by the user at the second server.

In 502, the first service party performing charging on the charging object may obtain the charging object from the service end. If the server synchronizes the charging information to the client, the first server for charging the charging object can also obtain the charging object locally at the client. The judgment result of whether the first service party is one of the at least one first service party associated with the second service party can be made by the client side or can be fed back to the client side by the service side; the embodiment of the present application is not particularly limited to this.

In an implementation example, in an application scenario where a parking lot cooperates with a shopping mall, when the parking lot is one of at least one parking lot cooperating with the shopping mall, the deduction data is displayed on the payment page of the client, as shown in the figure. When the parking lot is not one of at least one parking lot cooperating with the shopping mall, the payment page of the client does not display the deduction items and corresponding deduction data; or displaying the deduction items and enabling the corresponding deduction data of each item to be 0; or gradation display of each exemption term, etc. As shown in fig. 3, the exemption item may include a membership item, a shopping exemption item, a credit deduction item, and the like. The shopping exemption item can be used for acquiring the offline consumption data of the user by clicking a 'scanning receipt bar code' control key and reading a two-dimensional code entering a code scanning interface. When the parking lot is not one of the at least one parking lot cooperating with the mall, the 'swipe ticket barcode' control key is not displayed or is in a non-touchable state.

In the above 503, the payment data may be determined according to corresponding contents in the above embodiments, and details are not described herein.

Further, the method provided by this embodiment may further include:

504. and acquiring at least one charging object bound with the user.

505. Selecting a billing object from the at least one billing object.

Correspondingly, the displaying of the page element corresponding to the charging object in the payment interface in 501 specifically includes:

and displaying the page element corresponding to the selected charging object in the payment interface.

Further, the method provided by this embodiment may further include:

506. when the user is a registered user of the second service party, the registered exclusive share data provided by the second service party to the registered user is used as the exemption data; and/or

507. Acquiring offline consumption data generated by a user at the second service party, and converting the offline consumption data into exemption data; and/or

508. And acquiring accumulated data generated at the second server in the user history period, and converting the accumulated data into the exemption data.

The above acquiring offline consumption data generated by the user at the second service provider may specifically include:

responding to the operation of touching a code scanning control key in the payment interface by a user, entering a code scanning interface, reading data information corresponding to a code scanning object in a code scanning area in the code scanning interface, and determining the offline consumption data based on the data information; and/or

And responding to the operation of touching the shooting control key in the payment interface by a user, entering a shooting interface, collecting an image corresponding to a shooting object in a shooting collection area, and determining the offline payment data based on the image.

Further, the method provided by this embodiment further includes:

509. and responding to the operation of a user touching a confirmation control key in the payment interface, sending a payment request to a server so that the server executes the operation of submitting the payment data to the first service party, and displaying the execution result of the server.

Further, the method provided by this embodiment may further include:

510. when the execution result of the server is successful, receiving and displaying recommendation information determined by the server for the user based on the historical behavior data of the user; or

511. And when the execution result of the server side is successful, determining recommendation information for the user based on the locally stored historical line data of the user.

Based on 510 and 511, in the method provided in the embodiments of the present application, an execution subject for determining recommendation information for a user may be a server or a server, which is not specifically limited in this embodiment of the present application. For the historical behavior data and how to determine recommendation information for the user based on the historical behavior data, reference may be made to relevant contents in the above embodiments, which are not described herein again.

What needs to be added here is: the method provided by the embodiment can be applied to application scenes of cooperation of parking lots and shopping malls. Namely, the charging object is a vehicle; the first service party is a parking lot operator providing parking service for the vehicle; the second facilitator is an on-premise facilitator that provides off-line and/or on-line consumption services for the user.

The above embodiments have been described from the system, the client side, the server side, and the first server side, respectively. The technical scheme provided by the embodiment of the application can be simply summarized as follows: and the user uses the discount provided by the second service party through the client to reduce and exempt the discount of the total charging amount generated by the charging object applying payment for the user at the first service party. Substituting the technical scheme that this application embodiment provided into parking area and market cooperation's application scene, the technique can simply summarize to: after the user stops the vehicle in a parking lot cooperating with the shopping mall, the user can provide the user with the preference through the shopping mall by using the client, so that the preference and the avoidance of the parking fee of the vehicle in the parking lot are reduced.

The technical solution provided by the embodiment of the present application is further described below with reference to specific application scenarios (i.e., parking lot and shopping mall cooperation scenarios) to help understanding. The technical scheme provided by the embodiment of the application can be realized under one service platform (namely, a service end), and the first service party and the second service party are both resident in the service platform and maintain the association relationship at the service platform side. The user enjoys preferential service given to the user to park in the cooperative parking lot by a shopping mall through the client provided by the service platform.

The shopping mall and the at least one cooperative parking lot parking service platform are built in advance, and the association relationship between the shopping mall and the at least one parking lot is built at the service end. The server side can synchronize the association relationship between the shopping mall and the at least one parking lot to the client side. In order to facilitate parking payment, the user may use the client to bind the user information with the license plate number (equivalent to the charging object in each of the above embodiments) of the vehicle driven by the user. After the binding is successful, when the user uses the system in the follow-up process, the charging object bound with the user can be automatically displayed in the payment interface, and the user does not need to manually input the charging object each time. Wherein, the binding process is as follows: the user can input user information and vehicle information to be bound through a binding interface provided by the client, the client sends a binding request to the server after clicking a control key for confirming binding in the binding interface, and the server executes binding operation on the user information and the vehicle information to be bound carried in the binding request and feeds back a binding success response to the client after the binding is successful.

Assume that a user drives a vehicle into parking lot a; the parking lot a acquires license plate information (such as a license plate number) of a vehicle of a user. And the parking lot A sends charging information related to the license plate to a server based on the license plate information. The charging information comprises license plate information and parking lot A information.

When the user prepares to go out of the parking lot, the user scans the two-dimensional code in the parking lot A by touching a code scanning control key on a corresponding interface of the mall B, and jumps to a parking payment interface (as shown in FIG. 3) after the scanning is successful; or after the user enters the corresponding interface of the mall B and shakes the terminal, jumping to the parking payment interface (as shown in fig. 3).

The parking lot staff informs the user of the total charging amount of the vehicle, and the user inputs the total charging amount on a payment page; or the client acquires the total charging amount of the user vehicle from the parking lot A through the server, and the parking payment interface automatically displays the acquired total charging amount.

If the parking lot a is one of at least one parking lot cooperating with the mall B, the exemption data is displayed on the payment page of the client, as shown in fig. 3. If the parking lot A is not one of the at least one parking lot cooperating with the market B, the payment page of the client does not display the deduction items and corresponding deduction data; or displaying the deduction items and enabling the corresponding deduction data of each item to be 0; or gradation display of each exemption term, etc. As shown, the exemption term can include a membership term, a shopping exemption term, a credit offset term, and the like.

The shopping exemption item user can click the control key of 'scanning receipt bar code', and the online consumption data of the user is obtained by reading the two-dimensional code entering the code scanning interface. As shown in fig. 3, the parking payment interface may further display rule information of offline consumption data conversion exemption data, so that the user can learn the preference rule provided by mall B, such as the rule information of "member consumes 200 yuan minus 6 yuan every time" displayed in shopping exemption in fig. 3. What needs to be added here is: the above-mentioned obtaining method of the exemption data can refer to the relevant contents in the above-mentioned embodiments, and is not described herein again.

And the service end can carry out the operation of paying the payment data to the parking lot A aiming at the user vehicle when the user clicks the confirmation payment in the interface. The process of the server executing the payment operation can refer to the existing network payment technology, and is not described herein again.

The server side feeds back execution result information to the parking lot A and the client side after executing the payment operation, if the execution result is successful payment, the parking lot A executes release operation, and the client side displays a payment success prompt; if the execution result is that the payment fails, the parking lot A outputs a failure prompt, and the client displays the payment failure prompt.

After the server executes the payment operation, if the execution result is that the payment is successful, determining recommendation information for the user based on the historical behavior data of the user, and displaying the recommendation information recommended for the user on a user interface, as shown in fig. 4.

Fig. 8 shows a schematic structural diagram of a payment device according to an embodiment of the present application. As shown in fig. 8, the payment device includes:

a first obtaining module 601, configured to obtain a first service party that charges a charging object;

a second obtaining module 602, configured to obtain, when the first service party is one of at least one first service party associated with a second service party, exemption data generated at the second service party by a user who applies for paying for the charging object;

a determining module 603, configured to determine, according to the exemption data and the total charging amount generated by the charging object, payment data that the user needs to pay the first service party.

Further, the first obtaining module 601 is further configured to: acquiring the first service party from a service end; or determining the first server based on the scanned code.

Further, the second obtaining module 602 is further configured to:

when the user is a registered user of the second service party, the registered exclusive share data provided by the second service party to the registered user is used as the exemption data; and/or

Acquiring offline consumption data generated by the user at the second service party, and converting the offline consumption data into exemption data; and/or

And acquiring accumulated data generated at the second server in the user history period, and converting the accumulated data into the exemption data.

Further, the second obtaining module 602 is further configured to: in response to a user-triggered code scanning event, determining the offline consumption data based on code scanning information; or in response to a user-triggered capture event, determining the offline consumption data based on the captured picture.

Further, the determining module 603 is further configured to: subtracting the exemption data from the total charging amount to obtain the payment data; or multiplying the total charging amount by the exemption data to obtain the payment data.

Further, the payment device may further include:

the first sending module is used for responding to a confirmation event triggered by the user aiming at the payment data, sending a payment request to a server so that the server carries out the operation of paying the payment data to the first server aiming at the charging object.

Further, the payment device may further include:

a third obtaining module, configured to obtain the total charging amount input by the user; or obtaining the billing sum from the first serving party.

Further, the payment device further comprises a recommendation module;

the recommendation module is used for acquiring historical behavior data of the user; determining recommendation information for the user according to the historical behavior data; and after the user successfully pays the payment data for the first service, outputting the recommendation information.

Still further, the recommending module is further configured to calculate portrait features of the user according to historical behavior data of the user, and determine first recommended content for the user according to the portrait features; and/or

Further, the charging object is a vehicle; the first service party is a parking lot operator providing parking service for the vehicle; the second facilitator is an on-premise facilitator that provides off-line and/or on-line consumption services for the user.

Here, it should be noted that: the payment device provided in the foregoing embodiment may implement the technical solution described in the method embodiment shown in fig. 2, and the specific implementation principle of each module or unit may refer to the corresponding content in the foregoing corresponding method embodiment, which is not described herein again.

Fig. 9 shows a schematic structural diagram of a payment device according to another embodiment of the present application. As shown in fig. 9, the payment device includes:

a first receiving module 701, configured to receive a payment request sent by a client, where the payment request carries a charging object, a first service party charging the charging object, and payment data;

an executing module 702, configured to execute, for the charging object, a payment operation of paying the payment data to the first service party;

Further, the payment module further includes:

the second receiving module is used for receiving and storing the charging information of the charging object uploaded by at least one first service party;

and the query module is used for feeding back a first service party which charges the charging object pointed by the acquisition request to the client side sending the acquisition request by querying the charging information.

Furthermore, the payment device further comprises a recommendation module. The recommending module is used for acquiring historical behavior data of the user applying for paying for the charging object; determining recommendation information for the user according to the historical behavior data; and after the payment operation is successful, sending the recommendation information to the client.

Here, it should be noted that: the payment device provided in the foregoing embodiment may implement the technical solution described in the method embodiment shown in fig. 4, and the specific implementation principle of each module or unit may refer to the corresponding content in the foregoing corresponding method embodiment, which is not described herein again.

Fig. 10 shows a schematic structural diagram of a payment device according to yet another embodiment of the present application. As shown in fig. 10, the payment device includes:

a charging module 801, configured to charge a charging object to obtain a total charging amount generated by the charging object;

a third receiving module 802, configured to receive a prompt message sent by the server after executing payment data for the charging object;

an output module 803, configured to output the prompt information;

Further, the payment device further includes:

and the second sending module is used for sending the charging information corresponding to the charging object to a server side to store the charging information in the server side when the charging object is monitored to enter the field.

Further, the charging object is a vehicle; the server is a service platform for providing solutions for the first service party and the second service party; the first service party is a parking lot operator providing parking service for the vehicle; the second facilitator is an on-premise facilitator that provides off-line and/or on-line consumption services for the user.

Here, it should be noted that: the payment device provided in the foregoing embodiment may implement the technical solution described in the method embodiment shown in fig. 6, and the specific implementation principle of each module or unit may refer to the corresponding content in the foregoing corresponding method embodiment, which is not described herein again.

Fig. 11 shows a schematic structural diagram of a payment device according to another embodiment of the present application. As shown in fig. 11, the payment device includes:

the first display module 901 is configured to display, in response to a payment event triggered by a user through a corresponding interface of a second service party, a page element corresponding to the charging object in a payment interface;

a second display module 902, configured to display, in the payment interface, exemption data generated by the user at the second service party when the first service party charging the charging object is one of at least one first service party associated with the second service party;

a third display module 903, configured to display payment data that the user needs to pay the first service party and is determined according to the exemption data and the total charging amount generated by the charging object.

Further, the payment device further includes:

the triggering module is used for triggering the payment event when monitoring that the user performs the specified action; or when monitoring that the user sends out the specified voice, triggering the payment event; or when the touch operation of the user on the appointed control key is monitored, the payment event is triggered.

Further, the payment device further includes:

a fourth obtaining module, configured to obtain at least one charging object bound to the user;

a selection module, configured to select a charging object from the at least one charging object;

correspondingly, the first display module is further configured to display a page element corresponding to the selected one of the billing objects in the payment interface.

Further, the payment device further includes: and a fifth obtaining module. The fifth obtaining module is configured to, when the user is a registered user of the second service provider, use the registered exclusive share data provided by the second service provider to the registered user as the exemption data; and/or acquiring offline consumption data generated by a user at the second service party, and converting the offline consumption data into the exemption data; and/or obtaining accumulated data generated at the second service party in the user history period, and converting the accumulated data into the exemption data.

Further, the fifth obtaining module is further configured to: responding to the operation of touching a code scanning control key in the payment interface by a user, entering a code scanning interface, reading data information corresponding to a code scanning object in a code scanning area in the code scanning interface, and determining the offline consumption data based on the data information; and/or responding to the operation of touching the shooting control key in the payment interface by a user, entering the shooting interface, acquiring an image corresponding to a shooting object in the shooting acquisition area, and determining the offline consumption data based on the image.

Further, the payment device further includes:

and the third sending module is used for responding to the operation of a user for touching a confirmation control key in the payment interface, sending a payment request to the server so that the server executes the operation of submitting the payment data to the first server and displaying the execution result of the server.

Furthermore, the payment device further comprises a recommendation module. The recommending module is used for receiving and displaying recommending information determined by the server for the user based on the historical behavior data of the user when the execution result of the server is successful; or when the execution result of the server side is successful, determining recommendation information for the user based on the locally stored historical line data of the user.

Here, it should be noted that: the payment device provided in the foregoing embodiment may implement the technical solution described in the method embodiment shown in fig. 7, and the specific implementation principle of each module or unit may refer to the corresponding content in the foregoing corresponding method embodiment, which is not described herein again.

Fig. 12 shows a schematic structural diagram of a client device according to an embodiment of the present application. As shown in fig. 12, the client device includes: a first memory 1101 and a first processor 1102, wherein,

the first memory 1101 for storing a program;

the first processor 1102, coupled to the first memory 1101, is configured to execute the program stored in the first memory 1101 to:

acquiring a first service party for charging a charging object;

The first memory 1101 may be configured to store other various data to support operations on the cloud device. Examples of such data include instructions for any application or method operating on the cloud device. The first memory 1101 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

When the first processor 1102 executes the program in the first memory 1101, the first processor 1102 may also implement other functions in addition to the above functions, which may be specifically referred to the description of the foregoing embodiments.

Further, as shown in fig. 12, the electronic apparatus further includes: a first communication component 1103, a first display 1104, a first power component 1105, a first audio component 1106, and the like. Only some of the components are schematically shown in fig. 12, and the electronic device is not meant to include only the components shown in fig. 12.

Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps or functions of the payment method provided in the foregoing embodiments when executed by a computer.

Fig. 13 shows a schematic structural diagram of a server device according to an embodiment of the present application. As shown in fig. 13, the server device includes: a second memory 1201 and a second processor 1202, wherein,

the second memory 1201 is used for storing programs;

the second processor 1202, coupled to the second memory 1201, is configured to execute the program stored in the second memory 1201, so as to:

The second memory 1201 may be configured to store various other data to support operations on the cloud device. Examples of such data include instructions for any application or method operating on the cloud device. The second memory 1201 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

When the second processor 1202 executes the program in the second memory 1201, in addition to the above functions, other functions may be implemented, and reference may be specifically made to the description of the foregoing embodiments.

Further, as shown in fig. 13, the electronic apparatus further includes: a second communication component 1203, a second display 1204, a second power component 1205, a second audio component 1206, and the like. Only some of the components are schematically shown in fig. 13, and the electronic device is not meant to include only the components shown in fig. 12.

Fig. 14 shows a schematic structural diagram of a first server device according to an embodiment of the present application. As shown in fig. 14, the first server apparatus includes: a third memory 1301 and a third processor 1302, wherein,

the third memory 1301 is used for storing programs;

the third processor 1302, coupled to the third memory 1301, is configured to execute the program stored in the third memory 1301 to:

outputting the prompt information;

The third memory 1301 may be configured to store various other data to support operations on the cloud device. Examples of such data include instructions for any application or method operating on the cloud device. The third memory 1301 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

When the third processor 1302 executes the program in the third memory 1301, in addition to the above functions, other functions may be implemented, and reference may be specifically made to the description of the foregoing embodiments.

Further, as shown in fig. 14, the electronic apparatus further includes: a third communication component 1303, a third display 1304, a third power component 1305, a third audio component 1306, and other components. Only some of the components are schematically shown in fig. 14, and it is not meant that the electronic device includes only the components shown in fig. 14.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A payment method is applicable to a client side and comprises the following steps:

acquiring a first service party for charging a charging object;

when the first service party is determined to be one of at least one first service party associated with a second service party through judgment, obtaining exemption data generated by a user applying for paying for the charging object at the second service party; the incidence relation between the second service party and the at least one first service party is maintained by the service end;

determining payment data which the user needs to pay to the first service party according to the exemption data and the total charging amount generated by the charging object;

wherein the second service provider is an in-dwelling facilitator that provides the offline consumption service for the user.

2. The method of claim 1, wherein obtaining the first server that charges the charging object comprises:

acquiring the first service party from a service end; or

Determining the first server based on the scanned code.

3. The method of claim 1, wherein obtaining exemption data generated at a second service party by a user who applies for payment of the billing object comprises:

4. The method of claim 3, wherein obtaining offline payment data generated by the user at the second service comprises:

5. The method according to any one of claims 1 to 3, wherein determining payment data to be paid by the user to the first service party according to the deduction data and the total amount charged by the charging object comprises:

6. The method of any of claims 1 to 3, further comprising:

and responding to a confirmation event triggered by the user aiming at the payment data, sending a payment request to a server so that the server carries out the operation of paying the payment data to the first service party aiming at the charging object.

7. The method of any of claims 1 to 3, further comprising:

acquiring the total charging amount input by the user; or

Obtaining the billing total from the first serving party.

8. The method of any of claims 1 to 3, further comprising:

acquiring historical behavior data of the user;

determining recommendation information for the user according to the historical behavior data;

and after the user successfully pays the payment data for the first service, outputting the recommendation information.

9. The method of claim 8, wherein determining recommendation information for the user based on the historical behavior data comprises:

10. The method according to any one of claims 1 to 3, wherein the charging object is a vehicle; the first service party is a parking lot operator providing parking service for the vehicle.

11. A payment method is applicable to a server side and comprises the following steps:

maintaining an association between the second service party and at least one first service party;

wherein the payment data is determined according to exemption data and a total charging amount generated by the charging object at the first service party; the exemption data is obtained from the second service party when the first service party is determined to be one of at least one first service party associated with the second service party through judgment, and is generated at the second service party by a user applying for paying for the charging object; the second service provider is an in-dwelling facilitator that provides the offline consumption service for the user.

12. The method of claim 11, further comprising:

receiving and storing charging information of a charging object uploaded by at least one first service party;

and feeding back a first service party which charges the charging object pointed by the acquisition request to the client side sending the acquisition request by inquiring the charging information.

13. The method of claim 11 or 12, further comprising:

acquiring historical behavior data of the user applying for paying for the charging object;

and after the payment operation is successful, sending the recommendation information to the client.

14. The method of claim 13, wherein determining recommendation information for the user based on the historical behavior data comprises:

15. The method according to claim 11 or 12, wherein the charging object is a vehicle; the first service party is a parking lot operator providing parking service for the vehicle.

16. A payment method, adapted for a first service party, comprising:

outputting the prompt information;

the payment data is determined according to the deduction data and the total charging amount; the server maintains an association relationship between a second server and at least one first server, and the exemption data is obtained from the second server when the first server which charges the charging object is determined to be one of the at least one first server associated with the second server through judgment, and is generated at the second server by a user who applies for paying for the charging object; the second service provider is an in-dwelling facilitator that provides the offline consumption service for the user.

17. The method of claim 16, further comprising:

and when the entering of a charging object is monitored, charging information corresponding to the charging object is sent to a server so as to be stored in the server.

18. The method according to claim 16 or 17, wherein the billing object is a vehicle; the server is a service platform for providing solutions for the first service party and the second service party; the first service party is a parking lot operator providing parking service for the vehicle.

19. A payment system, comprising:

the client is used for acquiring a first service party for charging the charging object; when the first service party is determined to be one of at least one first service party associated with a second service party through judgment, obtaining exemption data generated by a user applying for paying for the charging object at the second service party; determining payment data which the user needs to pay to the first service party according to the exemption data and the total charging amount generated by the charging object; the second service party is a resident service provider for providing offline consumption service for the user;

the server is used for maintaining the association relationship between the second server and at least one first server; receiving a payment request sent by the client, wherein the payment request carries the charging object, the first service party and the payment data; executing payment operation of paying the payment data to the first service party aiming at the charging object;

the first service party is used for charging the charging object to obtain the total charging amount generated by the charging object; receiving prompt information sent by the server after the server executes payment data for the charging object; and outputting the prompt information.

20. A payment system as claimed in claim 19, wherein the billing object is a vehicle; the server is a service platform for providing solutions for the first service party and the second service party; the first service party is a parking lot operator providing parking service for the vehicle.

21. A payment method, comprising:

responding to a payment event triggered by a user through a corresponding interface of a second service party, and displaying a page element corresponding to the charging object in the payment interface; the second service party is a resident service provider for providing offline consumption service for the user;

when the first service party which charges the charging object is determined to be one of at least one first service party associated with the second service party through judgment, displaying the exemption data generated by the user at the second service party in the payment interface; the incidence relation between the second service party and the at least one first service party is maintained by the service end;

22. A payment method as claimed in claim 21, further comprising:

23. The method of claim 21, further comprising:

acquiring at least one charging object bound with the user;

selecting a charging object from the at least one charging object; and

the displaying of the page elements corresponding to the charging objects in the payment interface includes:

24. The method of claim 21, further comprising:

Acquiring offline consumption data generated by a user at the second service party, and converting the offline consumption data into exemption data; and/or

25. The method of claim 24, wherein obtaining offline payment data generated by a user at the second service comprises:

26. The method of any one of claims 21 to 25, further comprising:

and responding to the operation of a user touching a confirmation control key in the payment interface, sending a payment request to a server so that the server executes the operation of submitting the payment data to the first service party, and displaying the execution result of the server.

27. The method of claim 26, further comprising:

when the execution result of the server is successful, receiving and displaying recommendation information determined by the server for the user based on the historical behavior data of the user; or

And when the execution result of the server side is successful, determining recommendation information for the user based on the locally stored historical line data of the user.

28. The method of claim 21, wherein the billing object is a vehicle; the first service party is a parking lot operator providing parking service for the vehicle.

29. A client device, comprising: a first memory and a first processor, wherein,

the first memory is used for storing programs;

acquiring a first service party for charging a charging object;

30. A server-side device, comprising: a second memory and a second processor, wherein,

the second memory is used for storing programs;

the payment data is determined according to exemption data and the total charging amount generated by the charging object at the first service party; the exemption data is obtained from the second service party when the first service mode is determined to be one of at least one first service party associated with the second service party through judgment, and is generated at the second service party by a user applying for paying for the charging object; the second service provider is an in-dwelling facilitator that provides the offline consumption service for the user.

31. A first server device, comprising: a third memory and a third processor, wherein,

the third memory is used for storing programs;

outputting the prompt information;