CN112907338A

CN112907338A - Service processing method and device

Info

Publication number: CN112907338A
Application number: CN202110387914.8A
Authority: CN
Inventors: 侯恩训
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-05-09
Filing date: 2020-05-09
Publication date: 2021-06-04
Anticipated expiration: 2040-05-09
Also published as: CN112907338B; CN111311383A; CN111311383B

Abstract

An embodiment of the present specification provides a service processing method and a device, where the service processing method includes: receiving a processing request submitted by a first user for a target service; acquiring first credit data of the first user according to a first user identifier carried in the processing request; determining a second user performing credit authorization of the target service to the first user under the condition that the first credit data does not meet credit admission conditions of the target service; judging whether second credit data of the second user meets the credit admission condition or not; and if so, creating a service order of the processing request, wherein the service order comprises a first sub-order of the first user and a second sub-order of the second user.

Description

Service processing method and device

The invention is filed on 20200509, with application number 202010384983.9, and is a divisional application entitled "service processing method and device".

Technical Field

The embodiment of the specification relates to the technical field of data processing, in particular to a service processing method and device.

Background

With the development of the internet, credit has a greater and greater influence on the life of users, many services need to use credit as admission conditions, and the convenience enjoyed by users in the services is also affected by the level of the credit.

Disclosure of Invention

In view of this, the embodiments of the present specification provide a service processing method. One or more embodiments of the present disclosure also relate to a business processing apparatus, a computing device, and a computer-readable storage medium to solve technical problems in the prior art.

In a first aspect of the embodiments of the present specification, a service processing method is provided, including:

receiving a processing request submitted by a first user for a target service;

acquiring first credit data of the first user according to a first user identifier carried in the processing request;

determining a second user performing credit authorization of the target service to the first user under the condition that the first credit data does not meet credit admission conditions of the target service;

judging whether second credit data of the second user meets the credit admission condition or not;

and if so, creating a service order of the processing request, wherein the service order comprises a first sub-order of the first user and a second sub-order of the second user.

Optionally, the determining a second user performing credit authorization of the target service to the first user includes:

judging whether the first user has an authorized mark of credit authorization;

if yes, determining the service type of the target service according to the service identifier carried in the processing request;

acquiring a credit authorization item of the first user according to the first user identifier;

judging whether a target credit authorization sub-item matched with the service type exists in the credit authorization items authorized by the first user; the credit authorization item comprises a credit authorization sub-item authorized by a user having a credit authorization relationship with the first user, and the credit authorization sub-item has a corresponding relationship with the service type;

and if so, determining any authorized user of the authorized users who perform credit authorization on the target credit authorization sub-item aiming at the first user as the second user.

Optionally, if the result of the substep of determining whether the first user has the authorized tag for credit authorization is negative, the following operations are performed:

and sending a notification of refusing the admission aiming at the target service to the first user.

inquiring a target credit authorization item for performing credit authorization on the first user by a target user corresponding to the target user identification according to the target user identification carried in the processing request;

determining the service type of the target service according to the service identifier carried in the processing request;

judging whether the target credit authorization item contains a target credit authorization sub-item matched with the service type;

and if so, determining the target user as the second user.

Optionally, if the result of the substep of determining whether the target credit authorization item includes the target credit authorization sub-item matched with the service type is not included, the following operations are performed:

judging whether a target credit authorization sub-item matched with the service type exists in the credit authorization items authorized by the first user;

and if so, determining any authorized user in the authorized users who perform credit authorization on the target credit authorization sub-item to the first user as the second user.

Optionally, a credit authorization sub-item in the credit authorization items is created by:

generating a credit authorization request based on a request creation instruction submitted by the first user to request credit authorization from the second user;

generating a credit authorization protocol for the second user to carry out credit authorization on the first user according to authorization information carried in an authorization instruction submitted by the second user aiming at the credit authorization request; the authorization information comprises authorization type information submitted by the second user according to the service type to be authorized shown in the request detail page of the credit authorization request;

creating and storing a credit authorization sub-item for the second user to perform credit authorization on the first user based on the authorization type information;

and adding an authorized mark for performing credit authorization on the first user by the second user according to the first user identification and the second user identification of the second user contained in the authorization information, and adding an authorization mark for performing credit authorization on the first user to the second user.

Optionally, the generating a credit authorization request based on the request creating instruction submitted by the first user to request credit authorization from the second user includes:

acquiring the request establishing instruction which is submitted by the first user and requests credit authorization to the second user; the request creating instruction carries the first user identification and the second user identification;

generating the credit authorization request corresponding to the request establishing instruction according to the first user identification and the second user identification;

pushing the credit authorization request to the second user.

Optionally, the generating a credit authorization request corresponding to the request creation instruction according to the first user identifier and the second user identifier includes:

encrypting according to the first user identification and the second user identification to obtain encrypted information;

and generating a credit authorization request corresponding to the request creation instruction according to the encrypted information.

Optionally, after the step of pushing the credit authorization request to the second user is executed, and before the step of generating a credit authorization protocol for the second user to perform credit authorization to the first user according to authorization information carried in an authorization instruction submitted by the second user for the credit authorization request is executed, the method further includes:

receiving a request response instruction submitted by a request responder aiming at the credit authorization request;

decrypting the encrypted information carried in the request response instruction to obtain the first user identifier and the second user identifier;

judging whether the request responder is the second user or not by comparing the second user identifier with a responder identifier carried in the request response instruction;

if yes, inquiring credit detail information of the second user according to the second user identification;

inquiring identity detail information of the first user according to the first user identification;

generating a request detail page of the credit authorization request according to the identity detail information and the credit detail information;

and displaying the request detail page to the second user.

Optionally, the second user identifier is compared with a responder identifier carried in the request response instruction, and whether the request responder is the second user is determined as no, and the following operations are executed:

and returning an unauthorized response notice aiming at the request response instruction to the request responder.

Optionally, after the step of creating the service order for processing the request is executed, the method further includes:

sending the first sub-order to the first user;

and sending the second sub-order to the second user and a service provider of the target service.

In a second aspect of the embodiments of the present specification, there is provided a service processing apparatus, including:

the receiving module is configured to receive a processing request submitted by a first user for a target service;

the acquisition module is configured to acquire first credit data of the first user according to a first user identifier carried in the processing request;

a determining module configured to determine a second user performing credit authorization of the target service to the first user if the first credit data does not satisfy a credit admission condition of the target service;

a judging module configured to judge whether second credit data of the second user meets the credit admission condition;

if yes, operating a creating module, wherein the creating module is configured to create a service order of the processing request, and the service order comprises a first sub-order of the first user and a second sub-order of the second user.

In a third aspect of embodiments of the present specification, there is provided a computing device comprising:

a memory and a processor;

the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to:

receiving a processing request submitted by a first user for a target service;

In a fourth aspect of the embodiments of the present specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the instructions are executed by a processor, the steps of the business processing method are implemented.

The specification provides a service processing method, based on a processing request submitted by a first user for a target service, judging whether first credit data of the first user meets a credit admission condition of the target service, determining a second user performing credit authorization for the target service to the first user if the first credit data does not meet the credit admission condition, judging whether second credit data of the second user meets the credit admission condition, and if so, creating a service order for the processing request, wherein the service order comprises a first sub-order of the first user and a second sub-order of the second user, so that when the first credit data of the first user does not meet the credit admission condition of the target service, based on the credit authorization from the second user to the first user, and when the second credit data of the second user meets the credit admission condition, the first user is enabled to create the service order of the target service on the name of the second user, so that the first user can enjoy the service convenience enjoyed by the second user based on credit authorization, and the service volume of the target service is increased.

Drawings

Fig. 1 is a processing flow diagram of a service processing method provided in an embodiment of the present specification;

fig. 2 is a process flow diagram of a service processing method applied to a shared bicycle service according to an embodiment of the present specification;

fig. 3 is a schematic diagram of a service processing apparatus provided in an embodiment of the present specification;

fig. 4 is a block diagram of a computing device according to an embodiment of the present disclosure.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

In this specification, a service processing method is provided, and one or more embodiments of the specification relate to a service processing apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.

An embodiment of a service processing method provided in this specification is as follows:

fig. 1 shows a processing flow chart of a service processing method provided according to an embodiment of the present specification, which includes steps S102 to S110.

Step S102, receiving a processing request submitted by a first user for a target service.

In practical application, when a user submits a processing request for a target service, whether the user meets a credit admission threshold for participating in the target service needs to be judged according to credit conditions of the user, for some users in underdeveloped regions, the credit of the users is generally not high due to the limitation of the environment and the consumption capacity, but relatives, friends and the like of the users possibly have high credit due to the fact that the users are located in more developed regions.

Specifically, the target service refers to a service or a product that provides convenience to a user by using a credit as an admission condition, for example, a credit consumption service, a shared bicycle service, a taxi renting service, a credit store service, and the like, which is not limited herein; correspondingly, the processing request may be a participation request requesting to participate in a target service, a transaction request for the target service, or an application request for a certain service right in the target service, and the like, which is not limited herein; the first user is a requester for requesting processing of the target service.

In specific implementation, the user platform for bearing the account data of the first user and the service platform for bearing the operation of the target service may be the same platform or different platforms, and if the platform is different, the target service may be embedded in the user platform in a third-party application manner and associated with the user platform, and in addition, the service platform may also be associated in a manner of obtaining the user data of the user on the user platform, which is not limited herein.

Taking the shared bicycle service as an example, after the user a submits a lease request for the shared bicycle service through the user platform, the user platform receives the lease request submitted by the user a.

Step S104, acquiring first credit data of the first user according to the first user identification carried in the processing request.

On the basis of receiving a processing request submitted by a first user for a target service, first credit data of the first user is obtained according to a first user identifier carried in the processing request, so that whether the first user meets a credit admission condition of the target service is judged according to the first credit data.

The first user identifier refers to identification information that can uniquely identify a first user, and specifically, the user identifier refers to an identifier that can uniquely identify one user; the first credit data refers to data that can be used for characterizing the credit of the first user, and specifically, the credit data may be credit points, credit grades, credit scores, and the like, which is not limited herein;

in specific implementation, the user platform performs credit evaluation on the user by collecting historical consumption data, overdue data and the like of the first user in the user platform and each third-party application program to obtain first credit data of the first user, and after receiving a processing request submitted by the first user and aiming at a target service, obtains the first credit data of the first user according to a first user identifier carried in the processing request.

Following the above example, after receiving the lease request submitted by the user a, the user platform, according to the first user identifier of the user a carried in the lease request: "u 01" to obtain the credit score of user A as 350.

Step S106, determining a second user performing credit authorization of the target service to the first user when the first credit data does not satisfy the credit admission condition of the target service.

On the basis of acquiring the first credit data of the first user, judging whether the first credit data meets the credit admission condition of the target service; and if the credit meets the condition that the credit of the first user meets the service convenience in the target service, directly creating a service order between the first user and a service provider of the target service, and if the credit does not meet the condition that the credit of the first user does not meet the service convenience in the target service, executing to determine a second user performing credit authorization on the target service to the first user.

The credit admission condition refers to a condition which is preset for a credit of a user and is required to be met by the user for enjoying certain service convenience in a target service, and specifically, the credit admission condition for a credit consumption service refers to a condition which is required to be met by the user for enjoying a certain credit consumption amount; the credit admission condition for the shared bicycle service is a condition which needs to be met by the credit of the user if the user wants to enjoy the exempt right.

In addition, other target services also have credit admission conditions preset for the credit of the user aiming at the service convenience enjoyed in the services; in practical applications, these credit admission conditions may also be different according to different target services, such as: for the shared bicycle service, the credit admission condition of the escort-free is that the credit score of the user reaches 700 points, and for the credit store service, the credit admission condition of the escort-free hotel is that the credit score reaches 650 points.

The credit authorization means that one user authorizes the service convenience in the service shared by the credit of the user to another user so that the other user can share the service convenience provided by the service in the authorized range on the basis of authorization; the second user is an authorized user who performs credit authorization to the first user aiming at the target service.

In practical applications, there may be one or more authorized users performing credit authorization to the first user, which is not limited herein.

According to the above example, after the credit score of the user a is obtained, whether the credit score of the user a meets the credit admission condition of the shared bicycle service is judged, the credit score of the user a is 350 minutes, the credit admission condition of the shared bicycle service is that the credit score reaches 700 minutes, and the credit score of the user a does not meet the credit admission condition, so that the user a does not meet the credit admission condition of the shared bicycle service, and a user B performing credit authorization on the shared bicycle service to the user a needs to be further determined.

In a specific implementation, the method for determining a second user performing credit authorization for a target service to a first user is various, and in a first optional implementation manner provided in the embodiment of this specification, determining the second user is specifically implemented in the following manner:

judging whether the first user has an authorized mark of credit authorization;

if not, indicating that no authorized user performing credit authorization to the first user exists, and sending a permission refusing notice aiming at the target service to the first user.

If so, indicating that an authorized user performing credit authorization to the first user exists, and determining the service type of the target service according to the service identifier carried in the processing request;

if not, the authorization user for performing credit authorization on the first user aiming at the service type of the target service does not exist;

if the authorization user exists, the authorization user performing credit authorization on the first user aiming at the service type of the target service is indicated to exist, and any authorization user performing credit authorization on the target credit authorization sub-item on the first user is determined as the second user.

Specifically, the authorized user is a user who performs credit authorization to the first user; correspondingly, the authorized mark is used for marking whether an authorized user performing credit authorization on the user exists in the user, and in specific implementation, when a user establishes a credit authorization relationship with other users, the authorized mark is added to both parties establishing the credit authorization relationship, the authorized mark is added to the authorized user, and the corresponding authorized mark is added to the authorized user performing the credit authorization on the user; in practical applications, the authorization token and the authorized token are independent of their corresponding authorized users and authorized users, that is, all authorization tokens may be consistent, and all authorized tokens may also be consistent, and furthermore, the authorization token may also be associated with a corresponding authorized user, and the authorized token may also be associated with an authorized user who performs credit authorization on the authorized user, that is, different authorized users or authorization tokens/authorized tokens corresponding to authorized users are different, which is not limited herein.

In addition, when a user establishes a credit authorization relationship with other users, a credit authorization sub-item corresponding to the service type is created through the service type authorized by the authorized user to the authorized user by the authorized user, and when the credit authorization sub-item exists, the credit authorization of the service type corresponding to the credit authorization sub-item to the authorized user is indicated by the authorized user.

The admission refusal notification means that the first user is refused to enjoy the service convenience of the target service, but the first user can still participate in the target service in other modes, taking the shared bicycle service as an example, the admission refusal notification can be 'hello, your credit is insufficient, no lease can be enjoyed, and you are asked to pay a deposit'.

The service identifier is identification information which can uniquely identify one service; the service type refers to a service type to which the target service belongs, for example, the service type to which the shared bicycle service belongs is a lease type, in practical application, in a user platform, a third-party service with an interface with the user platform is classified according to the service type, and the service type to which the service belongs can be determined through a service identifier of the service; the target credit authorization sub-item refers to a credit authorization sub-item matched with the service type of the target service.

It should be noted that, the number of authorized users who perform credit authorization on the target credit authorization sub-item of the first user may be one or multiple, and when there are multiple authorized users, any one of the authorized users is determined as the second user; in practical applications, the second user may also be determined according to the intimacy between the authorized user and the authorized user, or according to the credit level of the authorized user, which is not limited herein.

Following the above example, in the case where user a does not satisfy the credit admission condition for shared bicycle traffic, by querying user a for the presence of the authorized token: the user A is determined to have an authorized mark, which indicates that an authorized user for performing credit authorization on the user A exists, the service type of the shared bicycle service is determined to be a lease type according to a service identifier 'p 01' carried in a lease request, and a credit authorization item ai01 of the user A is obtained according to a first user identifier 'u 01' of the user A;

the credit authorization sub-item contained in the credit authorization item ai01 of the user a is: determining whether a target credit authorization sub-item matched with the lease type exists in the credit authorization item ai01, namely the target credit authorization sub-item is a lease type, which indicates that an authorized user performing credit authorization on the user A according to the lease type exists, inquiring that an authorized user performing credit authorization on the target credit authorization sub-item lease type to the user A is a user B according to the user identifier 'u 01' of the user A and the target credit authorization sub-item 'lease type', and determining the user B as a second user;

assuming that it is determined that the authorization flag does not exist for the user a, or the determination result of determining whether the target credit authorization sub-item matching the lease type exists in the credit authorization item ai01 is non-existent, an admission denial notification "user a is good" is sent to the user a for the shared bicycle service: you have insufficient credit and can not enjoy free-deposit, ask you to pay the deposit ".

In the embodiment of the specification, whether an authorized user performing credit authorization to the first user exists is determined by judging whether an authorized mark of the credit authorization exists in the first user, if no authorized user performing credit authorization to the first user exists, an admission refusing notice aiming at the target service is sent to the first user, the step of determining a second user is avoided being continuously executed subsequently, the efficiency of service processing is improved, whether an authorized user performing credit authorization to the first user aiming at the service type exists is determined by judging whether a target credit authorization sub-item matched with the service type of the target service exists in a credit authorization item authorized by the first user, and in the case that the authorized user performing credit authorization to the first user aiming at the service type exists, any authorized user in the authorized users is determined as the second user, the method and the device ensure the credit authorization range of the second user to the first user before judging whether the second user meets the credit admission condition of the target service, and further improve the reliability of service processing.

In a specific implementation, a credit authorization sub-item in the credit authorization item is created on the basis that a first user requests credit authorization from a second user and a credit authorization protocol between the first user and the second user is established, and the credit authorization sub-item is created and stored on the basis of the credit authorization protocol, so that query efficiency on an authorized service type is improved, and service processing efficiency is further improved.

Specifically, the request creating instruction is used for creating a credit authorization request; the credit authorization protocol refers to an authorization protocol for a second user to perform credit authorization to a first user, and the credit authorization protocol appoints information such as an authorization range, an authorization duration and the like for the second user to perform credit authorization to the first user, wherein the authorization range includes information such as an authorized service type and a service limit.

The service type to be authorized is the service type which is displayed to the second user on the request detail page of the credit authorization request and can be used for the second user to carry out credit authorization to the first user. In specific implementation, the service type to be authorized may be a service type obtained by classifying all services having interfaces with the user platform, or a service type obtained by classifying services that the current credit of the second user can enjoy service convenience; correspondingly, the authorization type information refers to authorization type information corresponding to the selected or input to-be-authorized service type, which is generated based on the selection or input of the to-be-authorized service type shown on the request detail page by the second user, for example, the to-be-authorized service type shown on the request detail page includes: the second user selects a lease type and a transaction type from the service types to be authorized displayed on the request detail page to perform credit authorization on the first user, and then the authorization type information is as follows: a lease type and a transaction type.

In addition, the second user may also select an authorization duration for the first user on the request detail page, in a specific implementation, if the current time is not within the time range of the authorization duration included in the credit authorization protocol, it indicates that the credit authorization of the second user for the first user has expired, and may delete the credit authorization sub-item, the added authorization token, and the authorized token created based on the credit authorization protocol, or add a corresponding expiration token, etc., without limitation.

According to the above example, before a user A submits a lease request for a shared bicycle to a shared bicycle service through a user platform, the user A submits a request creation instruction for requesting credit authorization to a user B through the user platform, the user platform generates a credit authorization request based on the request creation instruction, the user B selects 1 year from authorization duration displayed on a request detail page of the credit authorization request, selects a lease type and a transaction type from service types to be authorized, submits the authorization instruction after the selection is completed, the user platform creates a credit authorization protocol for the user B to perform credit authorization to the user A according to authorization information carried in the authorization instruction submitted by the user B, and according to authorization type information contained in the authorization information: lease type and transaction type, creating a credit authorization sub-item: lease type and transaction type, and add the corresponding authorized tag "authorized by credit 01" for user a and the corresponding authorized tag for user B.

Specifically, in an optional implementation manner provided by this specification, the generating a credit authorization request based on a request creation instruction submitted by a first user, where the generating a credit authorization request is based on a first user identifier of the first user and a second user identifier of a second user, and pushing the created credit authorization request to the second user, so that the second user can view and authorize the credit authorization request, the generating a credit authorization request based on the request creation instruction submitted by the first user and requesting credit authorization from the second user, includes:

pushing the credit authorization request to the second user.

The credit authorization request may be pushed to the second user in a form of a request link, or pushed to the second user in a form of a card containing the request link, where the credit authorization request includes a request link generated according to a first user identifier of the first user and a second user identifier of the second user, so that the second user may jump to a request detail page corresponding to the link by clicking the link.

Along the above example, after the user platform obtains the request creating instruction that the user a submits to request the credit authorization from the user B, the request creating instruction carries the first user identifier "u 01" of the user a and the second user identifier "u 02" of the user B, a credit authorization request is generated according to the two user identifiers, and the generated credit authorization request is pushed to the user B.

In order to protect privacy of a user, in a process of generating a credit authorization request corresponding to a request creation instruction according to a first user identifier and a second user identifier, the first user identifier and the second user identifier need to be encrypted to prevent others from seeing the credit authorization request in an optional implementation manner provided by the embodiment of the present specification, the generation of the credit authorization request corresponding to the request creation instruction is specifically implemented in the following manner:

The encryption processing is carried out according to the first user identification and the second user identification to obtain encryption information, an encryption algorithm is adopted to carry out encryption processing on the first user identification and the second user identification, and the encryption algorithm is not limited; and generating a credit authorization request according to the encrypted information generated after encryption.

Along the above example, after the user platform obtains the request creating instruction that the user a submits to the user B to request credit authorization, the first user identifier "u 01" of the user a and the second user identifier "u 02" of the user B are carried in the request creating instruction, encryption processing is performed, an encryption character string is generated, and the credit authorization request is generated according to the encryption character string.

On the basis of pushing a credit authorization request to a second user, before the second user authorizes the credit authorization request, it is necessary to respond to the credit authorization request, and in the process of responding to the credit authorization request, perform identity verification on a request responder responding to the credit authorization request, and in the case that the identity verification passes, display a request detail page, which increases security in the credit authorization process and guarantees information security of the user, in an optional implementation manner provided by this specification, before generating a credit authorization protocol for performing credit authorization on the first user by the second user according to authorization information carried in an authorization instruction submitted by the second user for the credit authorization request, the method further includes:

if not, indicating that the request responder does not have permission to open the credit authorization request, and returning a permission-free response notice aiming at the request response instruction to the request responder;

if yes, the request responder is indicated to have the authority to open a credit authorization request, and the credit detail information of the second user is inquired according to the second user identification;

and displaying the request detail page to the second user.

In practical applications, after the generated credit authorization request is pushed to the user B, a situation that the credit authorization request is forwarded may occur, in this case, the request responder responding to the credit authorization request is not the second user, and therefore, after the request responder responds to the credit authorization request, and before a request detail page of the credit authorization request is displayed to the request responder, identity verification needs to be performed on the request responder.

Specifically, the identity detail information refers to information that can indicate the identity of the first user, such as: the information of the name, sex, age, occupation, identity code, etc. of the first user is not limited herein, the credit detail information includes credit data of the second user, and the second user can enjoy the information of the affiliated service type, etc. which is convenient for the service based on the credit, and is not limited herein.

The no-permission response notification is a notification for reminding the requesting responder that the requesting responder does not have permission to respond to the credit authorization request, for example, "hello, you have no permission to open the credit authorization request".

Along the above example, after the generated credit authorization request is pushed to the user B, a request response instruction submitted by a request responder for the credit authorization request is received, an encrypted string carried in the request response instruction is decrypted, a first user identifier "u 01" and a second user identifier "u 02" are generated, and whether the request responder is a second user is judged by comparing the second user identifier "u 02" with a responder identifier "u 02" carried in the request response instruction, and since the second user identifier "u 02" is the same as the responder identifier "u 02", it is determined that the request responder is the user B, which indicates that the request responder has authority to open the credit authorization request, and according to the second user identifier "u 02", the credit detail information of the user B is queried, including: credit score 750, the types of services enjoyed to facilitate the services are: the identity detail information of the user A is inquired according to the lease type, the transaction type and the guarantee type and the first user identification 'u 01', and comprises the following steps: name: name1, gender woman, identity code: id01, and generating a request detail page of the credit authorization request according to the inquired credit detail information of the user B and the identity detail information of the user A, and displaying the generated request detail page to the user B.

In addition to the foregoing specific implementation manner of determining a second user performing credit authorization for a target service to a first user, in a second optional implementation manner provided by this specification, the determining a second user performing credit authorization for the target service to the first user includes:

if not, the target user does not carry out credit authorization to the first user aiming at the service type of the target service;

and if the credit authorization is contained, the target user is determined as the second user according to the service type of the target service, wherein the credit authorization is performed on the first user by the target user aiming at the service type of the target service.

In practical application, a first user selects a target user for performing credit authorization before submitting a processing request for a target service, the submitted processing request carries a target user identifier of the target user, under the condition that first credit data of the first user does not meet credit admission conditions of a target page, a target credit authorization item for performing credit authorization on the first user by the target user is inquired according to the target user identifier carried in the processing request, whether the target credit authorization item contains the target credit authorization item for performing credit authorization on the first user according to the service type of the target service is judged, and if the target credit authorization item does not contain the target credit authorization item, the target user does not perform credit authorization on the first user according to the service type of the target service; and if the credit authorization is contained, the target user is determined as the second user according to the service type of the target service, wherein the credit authorization is performed on the first user by the target user.

Specifically, the target credit authorization item is similar to the credit authorization item, and refers to the credit authorization item for the target user to perform credit authorization to the first user.

Along the above example, when the user a does not satisfy the credit admission condition of the shared bicycle service, according to the target user identifier "u 02" carried in the lease request, a target credit authorization item for the target user corresponding to the target user identifier "u 02" to perform credit authorization to the user a is queried, where the target credit authorization item includes a credit authorization sub-item: determining that the service type of the shared bicycle service is a lease type according to a service identifier 'p 01' carried in the lease request, and judging that the target credit authorization item comprises a target credit authorization sub-item matched with the lease type: and determining the target user as the user B according to the lease type.

In the embodiment of the present specification, whether a target credit authorization item corresponding to a target user identifier, which is used for performing credit authorization on a first user by the target user, includes a target credit authorization sub-item that matches a service type of a target service is determined according to the target user identifier carried in a processing request submitted by the first user for the target service, and if the target credit authorization sub-item includes the target credit authorization sub-item, the target user is determined as a second user, so that the target user to which the first user can perform credit authorization can be selected as the second user, and flexibility of service processing is increased.

In an optional implementation manner provided by the embodiment of the present specification, when the target credit authorization item does not include the target credit authorization sub-item that matches the service type of the target service, the following operations are performed:

if the authorization user exists, the authorization user performing credit authorization on the first user according to the service type of the target service is indicated to exist, and any authorization user performing credit authorization on the target credit authorization sub-item from the first user is determined as the second user.

In practical application, if the target user selected by the first user does not perform credit authorization on the service type to which the target service belongs to the first user, it needs to be determined whether other authorized users performing credit authorization on the service type to which the first user belongs exist, and if not, it indicates that there is no authorized user performing credit authorization on the first user for the service type; if the service type of the second user exists, the service type of the second user is determined to be the service type of the first user, and if the service type of the second user exists, the service type of the second user is determined to be the service type of the first user.

In the above example, in the case that the target credit authorization item does not include the target credit authorization sub-item matching the lease type, the credit authorization item ai01 of the user a is obtained according to the first user identifier "u 01" of the user a, and the credit authorization sub-item included in the credit authorization item ai01 of the user a is: and (3) judging whether a target credit authorization sub-item matched with the lease type exists in the credit authorization item ai01, namely judging that the target credit authorization sub-item is the lease type, indicating that an authorized user for performing credit authorization on the user A according to the lease type exists, inquiring that the authorized user for performing credit authorization on the target credit authorization sub-item 'lease type' on the user A is a user B according to the user identifier 'u 01' of the user A and the target credit authorization sub-item 'lease type', and determining the user B as a second user.

In the embodiment of the specification, in the target credit authorization item for the target user to perform credit authorization to the first user corresponding to the target user identification, in the case where a target credit authorization sub-item matching the service type of the target service is not included, determining whether an authorized user performing credit authorization to the first user for the service type exists by judging whether a target credit authorization sub-item matched with the service type of the target service exists in the credit authorization items authorized by the first user, and in the event that it is determined that there is an authorized user who credit authorizes the first user for the type of service, any authorized user in the authorized users is determined as the second user, so that the credit authorization range of the second user to the first user is guaranteed before whether the second user meets the credit admission condition of the target service is judged, and the reliability of service processing is further improved.

Step S108, determining whether the second credit data of the second user meets the credit admission condition.

Specifically, on the basis of determining a second user performing credit authorization on a target service to a first user, whether second credit data of the second user meets a credit admission condition of the target service is judged, if yes, it indicates that the first user can enjoy service convenience provided by the target service based on the credit authorization of the second user, the following step S110 is executed, and if not, it indicates that neither the first user nor the second user meets the credit admission condition of the target service, and cannot enjoy the service convenience provided by the target service based on credit.

The second credit data, similar to the first credit data, refers to data that may be used to characterize a second user's credit. In addition, the specific implementation of judging whether the second credit data of the second user meets the credit admission condition is similar to the specific implementation of judging whether the first credit data of the first user meets the credit admission condition of the target service, and reference may be made to the specific implementation of judging whether the first credit data of the first user meets the credit admission condition of the target service, which is not described herein again.

In the above example, after the user B is determined as the second user, the credit score of the user B is 750 minutes, and the credit admission condition of the shared bicycle service is that the credit score reaches 700 minutes, it is determined that the user B meets the credit admission condition of the shared bicycle service, which indicates that the user a can enjoy the escort-free service provided by the shared bicycle service based on the credit authorization of the user B.

Step S110, creating a service order of the processing request, where the service order includes a first sub-order of the first user and a second sub-order of the second user.

And under the condition that the second credit data of the second user meets the credit admission condition of the target service, creating a service order according to the processing request submitted by the first user.

Specifically, the service order is a service order signed between a user and a target service provider and corresponding to a processing request, and the service order includes a first sub-order of the first user and a second sub-order of the second user, where the first sub-order is a service order signed between the first user and the target service provider, and the second sub-order is a service order signed between the second user and the target service provider.

In practical applications, an actual participant of the service order is the first user, but the credit data of the first user is not qualified for signing the service order, so that the first user can sign the service order with the provider of the target service on the behalf of the second user based on the credit authorization of the second user to the first user, in which case two sub-orders are generated, one is the first sub-order signed by the first user and the service provider of the target service, and the other is the second sub-order signed by the second user and the service provider of the target service.

Along the above example, in the case that the credit score of the user B meets the credit admission condition of the shared-bicycle service, a exempt order corresponding to the lease request is created, and the exempt order includes a exempt lease sub-order o1 signed by the user a and the service provider of the shared-bicycle service, and a exempt lease sub-order o2 signed by the user B and the service provider.

In order to ensure that each participant of the target service, that is, the first user, the second user, and the service provider can understand and track the signed service order, in an optional implementation manner provided in this specification, after the service order of the processing request is created, the created service order needs to be sent to the user, which is specifically implemented in the following manner:

sending the first sub-order to the first user;

In practical application, the first sub-order is used for the first user to know and track the processing progress of the business processing, and the second sub-order is used for the business provider of the target business and the second user to know and track the processing progress of the business processing, so that the first sub-order is sent to the first user, the second sub-order is sent to the second user and the business provider, that is, for the business provider, the second user signs a business order with the business provider, and the first user is shielded from the business provider.

Following the above example, after creating escort exempted lease sub-order o1 and escort exempted lease sub-order o2 contained in the escort exempted lease order, user a is sent an escort exempted lease sub-order o1 and user B and the service provider are sent an escort exempted lease sub-order o 2.

To sum up, the present specification provides a service processing method, which, based on a processing request submitted by a first user for a target service, first determines whether first credit data of the first user satisfies a credit admission condition of the target service, determines a second user performing credit authorization for the target service to the first user if the first credit data does not satisfy the credit admission condition, then determines whether second credit data of the second user satisfies the credit admission condition, and if so, creates a service order of the processing request, wherein the service order includes a first sub-order of the first user and a second sub-order of the second user, and when the first credit data of the first user does not satisfy the credit admission condition of the target service, based on the credit authorization from the second user to the first user, and when the second credit data of the second user satisfies the credit admission condition, the first user is enabled to create the service order of the target service on the name of the second user, so that the first user can enjoy the service convenience enjoyed by the second user based on credit authorization, and the service volume of the target service is increased.

The service processing method provided in this specification is further described below with reference to fig. 2, taking an application of the service processing method in a shared bicycle service as an example. Fig. 2 shows a processing flowchart of a service processing method applied to a shared bicycle service according to an embodiment of the present specification, and specific steps include step S202 to step S256.

The execution main body of the method embodiment is a user platform, credit authorization from a second user to a first user is established through interaction among the user platform, the first user and the second user, and service processing is carried out aiming at a renting request submitted by the first user for a shared bicycle service.

Step S202, a request creating instruction which is submitted by a first user and requests a second user for credit authorization is received.

Specifically, the request creation instruction carries a first user identifier of the first user and a second user identifier of the second user.

Step S204, encryption processing is carried out according to the first user identification of the first user and the second user identification of the second user, and encryption information is obtained.

Step S206, generating a credit authorization request corresponding to the request creation instruction according to the encrypted information.

Step S208, pushing the credit authorization request to the second user.

Step S210, receiving a request response instruction submitted by the request responder for the credit authorization request.

Step S212, carrying out decryption processing on the encrypted information carried in the request response instruction to obtain a first user identifier and a second user identifier;

step S214, judging whether the request responder is a second user or not by comparing the second user identifier with the responder identifier carried in the request response instruction;

if yes, indicating that the request responder is the second user, executing the following step S216;

if not, indicating that the request responder is not the second user, and returning an unauthorized response notice aiming at the request response instruction to the request responder.

And step S216, inquiring the credit detail information of the second user according to the second user identification.

Step S218, querying identity detail information of the first user according to the first user identifier.

Specifically, the execution order of step S216 and step S218 may be interchanged, and is not limited herein.

Step S220, a request detail page of the credit authorization request is generated according to the identity detail information and the credit detail information.

Step S222, the request detail page is displayed to the second user.

Step S224, according to the authorization instruction submitted by the second user for the credit authorization request.

Step S226, according to the authorization information carried in the authorization instruction, a credit authorization protocol is generated for the second user to perform credit authorization to the first user.

Specifically, the authorization information includes authorization type information submitted by the second user for the service type to be authorized shown in the request detail page of the credit authorization request.

Step S228, sending the credit authorization agreement to the first user.

Step S230, sending the credit authorization agreement to the second user.

Specifically, the execution order of step S228 and step S230 may be interchanged, and is not limited herein.

Step S232, based on the authorization type information included in the authorization information, creating and storing a credit authorization sub-item for the second user to perform credit authorization to the first user.

Step S234, according to the first user identifier and the second user identifier included in the authorization information, adds an authorization token for performing credit authorization on the first user by the second user, and adds an authorization token for performing credit authorization on the second user by the first user.

Step S236, a rental request submitted by the first user for the shared bicycle service is received.

Step S238, obtaining the first credit data of the first user according to the first user identifier carried in the lease request.

Step S240, under the condition that the first credit data does not meet the credit admission condition of the shared bicycle service, judging whether the first user has an authorized mark of credit authorization;

if not, indicating that no authorized user performing credit authorization to the first user exists, and sending a credit evaluation result aiming at the first user to the first user;

if yes, it indicates that there is an authorized user performing credit authorization to the first user, and the following step S242 is performed.

Step S242, determining the service type of the shared bicycle service according to the service identifier carried in the lease request.

Step S244, obtaining the credit authorization item of the first user according to the first user identifier.

Step S246, judging whether a target credit authorization sub-item matched with the service type exists in the credit authorization items authorized by the first user;

if the shared bicycle service does not exist, the fact that an authorized user performing credit authorization on the first user aiming at the service type of the shared bicycle service does not exist is shown;

if the service type of the shared bicycle service is the authorized user, the first user is subjected to credit authorization, and the following step S248 is executed.

Specifically, the credit authorization item includes a credit authorization sub-item authorized by a user having a credit authorization relationship with the first user, and the credit authorization sub-item has a corresponding relationship with the service type.

Step S248, any authorized user of the authorized users who perform credit authorization on the target credit authorization sub-item to the first user is determined as the second user.

Step S250, judging whether the second credit data of the second user meets the credit admission condition;

if the result is satisfied, indicating that the first user can enjoy the service convenience provided by the shared bicycle service based on the credit authorization of the second user, the following step S252 is executed;

if the credit access condition does not meet the requirement, the first user and the second user do not meet the credit access condition of the shared bicycle service, and the escort-free use convenience provided by the shared bicycle service based on the credit cannot be enjoyed.

Step S252, a exempt lease order for the lease request is created.

Specifically, the service order includes a first sub-order of the first user and a second sub-order of the second user.

Step S254, the first sub-order is sent to the first user.

And step S256, transmitting the second sub-order to the second user and a service provider sharing the bicycle service.

Specifically, the execution order of step S254 and step S256 may be interchanged, and is not limited herein.

An embodiment of a service processing apparatus provided in this specification is as follows:

corresponding to the above method embodiment, the present specification further provides a service processing apparatus embodiment, and fig. 3 shows a schematic diagram of a service processing apparatus provided in an embodiment of the present specification. As shown in fig. 3, the apparatus includes:

a receiving module 302 configured to receive a processing request submitted by a first user for a target service;

an obtaining module 304, configured to obtain first credit data of the first user according to a first user identifier carried in the processing request;

a determining module 306 configured to determine a second user performing credit authorization of the target service to the first user if the first credit data does not satisfy a credit admission condition of the target service;

a determining module 308 configured to determine whether second credit data of the second user satisfies the credit admission condition;

if yes, running a creating module 310, where the creating module 310 is configured to create a service order of the processing request, where the service order includes a first sub-order of the first user and a second sub-order of the second user.

Optionally, the determining module 306 includes:

a determination flag submodule configured to determine whether there is an authorized flag of credit authorization for the first user;

if yes, operating a first type determining sub-module, wherein the first type determining sub-module is configured to determine the service type of the target service according to a service identifier carried in the processing request;

a first obtaining authorization item sub-module configured to obtain a credit authorization item of the first user according to the first user identifier;

a first judging authorization sub-item sub-module, configured to judge whether a target credit authorization sub-item matching the service type exists in the credit authorization items authorized by the first user; the credit authorization item comprises a credit authorization sub-item authorized by a user having a credit authorization relationship with the first user, and the credit authorization sub-item has a corresponding relationship with the service type;

and if so, operating a first user-determining sub-module, wherein the first user-determining sub-module is configured to determine any authorized user of the authorized users who perform credit authorization on the target credit authorization sub-item for the first user as the second user.

Optionally, if the judgment result output by the judgment marking sub-module is negative, the following sub-modules are operated:

a transmission notification sub-module configured to transmit a notification of denial of admission for the target traffic to the first user.

Optionally, the determining module 306 includes:

a target authorization item query submodule configured to query, according to a target user identifier carried in the processing request, a target credit authorization item for performing credit authorization on the first user by a target user corresponding to the target user identifier;

a second type determining submodule configured to determine a service type of the target service according to a service identifier carried in the processing request;

a second judgment authorization sub-item sub-module configured to judge whether the target credit authorization item includes a target credit authorization sub-item matched with the service type;

and if so, operating a second determined user sub-module, wherein the second determined user sub-module is configured to determine the target user as the second user.

Optionally, if the judgment result output by the first judgment target authorization item sub-module does not contain any of the following sub-modules:

a second obtaining authorization item submodule configured to obtain a credit authorization item of the first user according to the first user identifier;

a third judging authorization sub-item sub-module, configured to judge whether a target credit authorization sub-item matching the service type exists in the credit authorization items authorized by the first user;

and if so, operating a third determined user sub-module, wherein the third determined user sub-module is configured to determine any authorized user in the authorized users who perform credit authorization on the target credit authorization sub-item to the first user as the second user.

Optionally, a credit authorization sub-item in the credit authorization items is created by operating the following modules:

a generation request module configured to generate a credit authorization request based on a request creation instruction submitted by the first user to request credit authorization from the second user;

a generation protocol module configured to generate a credit authorization protocol for the second user to perform credit authorization on the first user according to authorization information carried in an authorization instruction submitted by the second user for the credit authorization request; the authorization information comprises authorization type information submitted by the second user according to the service type to be authorized shown in the request detail page of the credit authorization request;

a creating authorization sub-item module configured to create and store a credit authorization sub-item for the second user to perform credit authorization to the first user based on the authorization type information;

and the authorization mark adding module is configured to add an authorized mark for performing credit authorization on the first user by the second user according to the first user identification and the second user identification of the second user, which are contained in the authorization information, to the first user, and add an authorization mark for performing credit authorization on the first user to the second user.

Optionally, the request generating module includes:

a get instruction submodule configured to get the request creation instruction submitted by the first user to request credit authorization from the second user; the request creating instruction carries the first user identification and the second user identification;

an authorization request generation submodule configured to generate the credit authorization request corresponding to the request creation instruction according to the first user identifier and the second user identifier;

a push user sub-module configured to push the credit authorization request to the second user.

Optionally, the generate authorization request sub-module includes:

the encryption unit is configured to perform encryption processing according to the first user identification and the second user identification to obtain encryption information;

and the generation authorization request unit is configured to generate a credit authorization request corresponding to the request creation instruction according to the encrypted information.

Optionally, the service processing apparatus further includes:

a receiving response instruction module configured to receive a request response instruction submitted by a request responder for the credit authorization request;

the decryption module is configured to decrypt the encrypted information carried in the request response instruction to obtain the first user identifier and the second user identifier;

the second user judging module is configured to judge whether the request responder is the second user by comparing the second user identifier with a responder identifier carried in the request response instruction;

if yes, operating a credit detail inquiring module, wherein the credit detail inquiring module is configured to inquire the credit detail information of the second user according to the second user identification;

the identity detail inquiring module is configured to inquire identity detail information of the first user according to the first user identification;

a generation detail page configured to generate a request detail page of the credit authorization request according to the identity detail information and the credit detail information;

a presentation details page configured to present the request details page to the second user.

Optionally, the following module is operated when the judgment result output by the second user module is judged to be negative:

and the corresponding notification returning module is configured to return an unauthorized response notification aiming at the request response instruction to the request responder.

Optionally, the service processing apparatus further includes:

a first send sub-order module configured to send the first sub-order to the first user;

and the second sending sub-order module is configured to send the second sub-order to the second user and a service provider of the target service.

The specification provides a service processing device, based on a processing request submitted by a first user for a target service, firstly judging whether first credit data of the first user meets a credit admission condition of the target service, if the first credit data does not meet the credit admission condition, determining a second user performing credit authorization for the target service to the first user, then judging whether second credit data of the second user meets the credit admission condition, and if so, creating a service order of the processing request, wherein the service order comprises a first sub-order of the first user and a second sub-order of the second user, so that when the first credit data of the first user does not meet the credit admission condition of the target service, based on the credit authorization from the second user to the first user, and when the second credit data of the second user meets the credit admission condition, the first user is enabled to create the service order of the target service on the name of the second user, so that the first user can enjoy the service convenience enjoyed by the second user based on credit authorization, and the service volume of the target service is increased.

The foregoing is a schematic scheme of a service processing apparatus according to this embodiment. It should be noted that the technical solution of the service processing apparatus and the technical solution of the service processing method belong to the same concept, and details that are not described in detail in the technical solution of the service processing apparatus can be referred to the description of the technical solution of the service processing method.

The present specification provides an embodiment of a computing device as follows:

FIG. 4 illustrates a block diagram of a computing device 400 provided in accordance with one embodiment of the present description. The components of the computing device 400 include, but are not limited to, a memory 410 and a processor 420. Processor 420 is coupled to memory 410 via bus 430 and database 450 is used to store data.

Computing device 400 also includes access device 440, access device 440 enabling computing device 400 to communicate via one or more networks 460. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The access device 440 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the present description, the above-described components of computing device 400, as well as other components not shown in FIG. 4, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 4 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.

Computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 400 may also be a mobile or stationary server.

The present specification provides a computing device comprising a memory 410, a processor 420, and computer instructions stored on the memory and executable on the processor, the processor 420 being configured to execute the following computer-executable instructions:

receiving a processing request submitted by a first user for a target service;

The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the service processing method belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the service processing method.

This specification provides one example of a computer-readable storage medium, comprising:

the present specification provides a computer readable storage medium storing computer instructions that, when executed by a processor, are operable to:

receiving a processing request submitted by a first user for a target service;

The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the technical solution of the service processing method, and details that are not described in detail in the technical solution of the storage medium can be referred to the description of the technical solution of the service processing method.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts, but those skilled in the art should understand that the present embodiment is not limited by the described acts, because some steps may be performed in other sequences or simultaneously according to the present embodiment. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for an embodiment of the specification.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the embodiments. The specification is limited only by the claims and their full scope and equivalents.

Claims

1. A service processing method comprises the following steps:

receiving a processing request submitted by a first user for a target service;

in response to the processing request, under the condition that first credit data of the first user does not meet credit admission conditions of the target service, creating a service order of the target service based on second credit data of a second user, wherein the second user is a user performing credit authorization on the first user, and the service order comprises a first sub-order of the first user and a second sub-order of the second user;

and sending the first sub-order to the first user, and sending the second sub-order to the second user and the service provider of the target service, wherein the second sub-order refers to a service order signed by the second user and the service provider of the target service.

2. The service processing method according to claim 1, wherein the second user is determined by:

judging whether the first user has an authorized mark of credit authorization;

3. The service processing method according to claim 2, wherein the substep of determining whether the first user has the authorized token for credit authorization performs the following operations if the result of the determination is negative:

4. The service processing method according to claim 1, wherein the second user is determined by:

and if so, determining the target user as the second user.

5. The service processing method according to claim 4, wherein the sub-step of determining whether the target credit authorization item includes a target credit authorization sub-item matching the service type is performed with the following operations:

6. The transaction processing method according to claim 2, wherein a credit authorization sub-item in the credit authorization items is created by:

7. The transaction processing method according to claim 6, wherein generating a credit authorization request based on a request creation instruction submitted by the first user to request credit authorization from the second user comprises:

pushing the credit authorization request to the second user.

8. The service processing method according to claim 7, wherein the generating a credit authorization request corresponding to the request creation instruction according to the first subscriber identity and the second subscriber identity includes:

9. The service processing method according to claim 8, wherein after the step of pushing the credit authorization request to the second user is executed and before the step of generating a credit authorization protocol for the second user to perform credit authorization to the first user according to authorization information carried in an authorization instruction submitted by the second user for the credit authorization request is executed, the method further comprises:

and displaying the request detail page to the second user.

10. The service processing method according to claim 9, wherein the step of determining whether the request responder is the second user is performed in a manner of comparing the second user identifier with a responder identifier carried in the request response instruction, and if the determination result is negative, performing the following operations:

11. A traffic processing apparatus, comprising:

a creating module configured to, in response to the processing request, create a service order of the target service based on second credit data of a second user in a case that first credit data of the first user does not satisfy a credit admission condition of the target service, where the second user is a user who performs credit authorization on the first user, and the service order includes a first sub-order of the first user and a second sub-order of the second user; and sending the first sub-order to the first user, and sending the second sub-order to the second user and the service provider of the target service, wherein the second sub-order refers to a service order signed by the second user and the service provider of the target service.

12. A computing device, comprising:

a memory and a processor;

receiving a processing request submitted by a first user for a target service;

13. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the traffic processing method of any of claims 1 to 10.