CN116911945A

CN116911945A - Merchant category processing method and device

Info

Publication number: CN116911945A
Application number: CN202310871004.6A
Authority: CN
Inventors: 周燕
Original assignee: AlipayCom Co ltd
Current assignee: AlipayCom Co ltd
Priority date: 2023-07-14
Filing date: 2023-07-14
Publication date: 2023-10-20

Abstract

The embodiment of the specification provides a method and a device for processing a class of merchants, wherein the method for processing the class of the merchants comprises the following steps: acquiring transaction data of a merchant in a category verification period; determining a target merchant category based on the merchant data and the transaction data, and verifying whether the target merchant category is the same as the merchant category associated with the merchant; if not, updating the merchant category into the target merchant category according to a confirmation instruction of the merchant to the target merchant category; and constructing service labels of merchants according to the target merchant categories so as to perform service processing according to the service labels.

Description

Merchant category processing method and device

Technical Field

The present document relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing a class of merchants.

Background

With the development of network technology and communication technology, information networks become an important part of life, more and more merchants provide goods or services for users through the information networks, the users consume the goods or services provided by the merchants online or offline, and in the process of online or offline consumption of the merchants by the users, the users need to consume certain resources or other substances related to the users, so that higher requirements are provided for the accuracy and the effectiveness of online data of the merchants.

Disclosure of Invention

One or more embodiments of the present specification provide a merchant category processing method. The merchant category processing method comprises the following steps: transaction data of merchants in a category verification period is obtained. Determining a target merchant category based on merchant data and the transaction data, and verifying whether the target merchant category is the same as the merchant category of the merchant; if not, updating the merchant category into the target merchant category according to the confirmation instruction of the merchant to the target merchant category. And constructing a service label of the merchant according to the target merchant category so as to perform service processing according to the service label.

One or more embodiments of the present specification provide a merchant category processing apparatus comprising: and the data acquisition module is configured to acquire transaction data of the merchant in the category verification period. A category verification module configured to determine a target merchant category based on merchant data and the transaction data and verify whether the target merchant category is the same as a merchant category of the merchant; if not, a class updating module is operated, and the class updating module is configured to update the class of the merchant to the class of the target merchant according to the confirmation instruction of the merchant to the class of the target merchant. And the label construction module is configured to construct a service label of the merchant according to the target merchant category so as to perform service processing according to the service label.

One or more embodiments of the present specification provide a merchant category processing device comprising: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: transaction data of merchants in a category verification period is obtained. Determining a target merchant category based on merchant data and the transaction data, and verifying whether the target merchant category is the same as the merchant category of the merchant; if not, updating the merchant category into the target merchant category according to the confirmation instruction of the merchant to the target merchant category. And constructing a service label of the merchant according to the target merchant category so as to perform service processing according to the service label.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, implement the following: transaction data of merchants in a category verification period is obtained. Determining a target merchant category based on merchant data and the transaction data, and verifying whether the target merchant category is the same as the merchant category of the merchant; if not, updating the merchant category into the target merchant category according to the confirmation instruction of the merchant to the target merchant category. And constructing a service label of the merchant according to the target merchant category so as to perform service processing according to the service label.

Drawings

For a clearer description of one or more embodiments of the present description or of the solutions of the prior art, the drawings that are needed in the description of the embodiments or of the prior art will be briefly described below, it being obvious that the drawings in the description that follow are only some of the embodiments described in the present description, from which other drawings can be obtained, without inventive faculty, for a person skilled in the art;

FIG. 1 is a schematic illustration of one implementation environment provided by one or more embodiments of the present disclosure;

FIG. 2 is a process flow diagram of a method for merchant category processing according to one or more embodiments of the present disclosure;

FIG. 3 is a schematic diagram illustrating a method for processing a merchant category according to one or more embodiments of the present disclosure;

FIG. 4 is a process flow diagram of a business category processing method for a business category processing scenario according to one or more embodiments of the present disclosure;

FIG. 5 is a schematic diagram of one embodiment of a merchant category processing device provided in one or more embodiments of the present disclosure;

fig. 6 is a schematic structural diagram of a merchant category processing device according to one or more embodiments of the present disclosure.

Detailed Description

In order to enable a person skilled in the art to better understand the technical solutions in one or more embodiments of the present specification, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the drawings in one or more embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one or more embodiments of the present disclosure without inventive effort, are intended to be within the scope of the present disclosure.

The method for processing the category of the merchant provided in one or more embodiments of the present disclosure may be applied to an implementation environment of processing the category of the merchant, as shown in fig. 1, where the implementation environment includes at least a server 101 and a merchant 102; server 101 may interact data with merchant 102.

The server 101 may be one or more servers, a server cluster formed by a plurality of servers, or a cloud server of a cloud computing platform, and is configured to detect a class verification period of a merchant, and maintain merchant data and associated accurate merchant classes of the merchant.

Merchant 102, which may be a user or institution that cooperates with a target application corresponding to a server to develop a service of the merchant; the merchant can cooperate with the target application to pay the merchant based on the target application in the process of consuming the commodity or service of the merchant under the online condition of the user, and in addition, the merchant can cooperate with the target application to enable the target application to display the commodity or service provided by the merchant, so that the user consumes the commodity or service displayed by the target application; the merchant 102 cooperates with the target application, and needs to register the merchant in the server 101, and the merchant can cooperate with the target application corresponding to the server 101 after registering.

In addition, the implementation environment may further include a user terminal 103, where the user terminal 103 may be a smart phone, a tablet computer, an electronic book reader, a wearable device, an AR (Augmented Reality) based/VR (Virtual Reality) based device, or the like, and may further be provided with an application program or a browser of a target application, through which a transaction with the merchant 102 is performed.

In this implementation environment, after the class verification period of the merchant 102 expires, the server 101 determines a target merchant class based on the merchant data of the merchant 102 and the transaction data of the merchant 102 in the class verification period, updates the merchant class to the target merchant class if the target merchant class is different from the merchant class associated with the merchant 102, and constructs a service tag of the merchant 102 according to the target merchant class, so as to perform service processing according to the service tag.

One or more embodiments of a merchant category processing method provided in the present specification are as follows:

according to the method for processing the merchant category, the target merchant category is determined according to the merchant data of the merchant and the transaction data in the category verification period, the merchant category associated with the merchant is updated to be the target merchant category under the condition that the determined target merchant category is different from the merchant category associated with the merchant, and the service tag of the merchant is constructed according to the target merchant category so as to perform service processing according to the service tag, so that timeliness of the merchant category associated with the merchant is improved through configuration of the category verification period, determination of the target merchant category is performed through the transaction data of the merchant in the category verification period, accuracy of the determined target merchant category is improved, validity of the target merchant category associated with the merchant is improved through updating the merchant category associated with the target merchant category, and convenience in use of the target merchant category associated with the merchant is improved.

Referring to fig. 2, the method for processing a merchant category provided in the present embodiment specifically includes steps S202 to S208.

Step S202, transaction data of merchants in a category verification period is obtained.

The present embodiment is applicable to a server of a target application, including a payment application. The merchant comprises a user or a mechanism which cooperates with the target application to develop the service of the merchant; in this embodiment, the class verification period includes a period obtained by dividing a time interval configured in advance. The transaction data comprises at least one data recording transaction behavior generated by taking a merchant as a transaction object in the class verification period. Optionally, the transaction data includes at least one of: transaction amount, resource transfer-out party, resource transfer-in party, transaction environment data. In addition, the transaction data may also include other data corresponding to transaction actions, such as transaction notes, transaction order information, and the like. The transaction object may be a resource transfer-out party or a resource transfer-in party.

In particular, in order to effectively manage the merchant, the merchant performs the service of the merchant in the target application, and the merchant registration is required to be performed in the target application, and after the merchant registration, the relevant data of the merchant is maintained and updated to perform the service of the merchant. In order to perform more effective and accurate management on the merchant, merchant registration is performed based on merchant data, wherein the merchant data can be proving data for representing the identity and the management authority of the merchant. Optionally, the merchant data includes at least one of: the business voucher, the business location, the merchant account and the merchant portal photograph. In addition, the information may further include information related to the merchant communication identifier, which is not limited herein. The business certificate comprises a certificate which is issued to a merchant by a merchant management mechanism and permits the merchant to conduct a certain production business, and at least one of the following is recorded in the business certificate: merchant name, business location, merchant associated user, merchant funds amount, economic components, business scope, business style, practitioner, business duration.

In a specific execution process, in the process of registering the merchant, besides merchant data, the merchant class associated with the merchant needs to be determined; in an optional implementation manner provided in this embodiment, before acquiring transaction data of a merchant in a category verification period, determining a merchant category associated with the merchant by adopting the following manner:

determining a recommended merchant category based on the business voucher contained in the merchant data;

and determining the recommended merchant category as the merchant category of the merchant according to the confirmation instruction of the merchant to the recommended merchant category.

Optionally, the merchant category refers to a business category of the business category, which characterizes the merchant, can be a merchant category code, is configured by the target application for the merchant, is used for marking the transaction environment, business scope and industry attribution of the merchant, and is an important basis for carrying out service risk and merchant risk management on the merchant.

Specifically, the merchant category is recommended to the merchant, and the recommended merchant category is taken as the merchant category of the merchant under the condition that the recommended merchant category is confirmed by the merchant.

In the process of registering the merchant, firstly acquiring merchant data submitted by the merchant, determining a recommended merchant category based on the business voucher contained in the merchant data, sending the recommended merchant category to the merchant, and determining the recommended merchant category as the merchant category of the merchant according to a confirmation instruction of the merchant to the recommended merchant category.

For example, the merchant name on the business license of the merchant is "xxx food limited liability company", and the business scope in the business license includes: sales: vegetables, fruits, artwork, cosmetics; determining the recommended merchant category of the merchant as food sales according to the commodity name and the operating range; in order to avoid that the determined recommended merchant category is directly used as the merchant category of the merchant to cause the distrust of the merchant and the deviation of the recommended merchant category, the recommended merchant category is sent to the merchant, and if a confirmation instruction of the merchant to the recommended merchant category is detected, the food sales is determined as the merchant category of the merchant.

In addition, the identification may not be performed by the merchant, that is, the recommended merchant category may be determined based on the business voucher included in the merchant data, and the recommended merchant category may be determined as the merchant category of the merchant.

After determining the category of the merchant, in order to ensure timeliness of the category of the merchant, avoid resource loss of the target application due to inconsistency between the actual transaction of the merchant and the category of the merchant, and reduce service effects of the merchant, in this embodiment, after registering the merchant, the category verification is performed on the merchant according to a category verification period, and in an alternative implementation provided in this embodiment, after taking the recommended category of the merchant as the category of the merchant, the following operations are further performed:

Determining a category verification period of the merchant based on the transaction time and a specific time interval of the transaction behavior under the condition that the transaction behavior of the merchant is detected;

if the category verification period is detected to expire, step S202 is executed to obtain transaction data of the merchant in the category verification period.

Specifically, after registering the merchant, the user may transact the merchant based on the target application or the merchant may transact based on the target application, determine a class verification period of the merchant based on a transaction event of the transaction behavior and a specific time interval in case that the transaction behavior of the merchant is detected, and acquire transaction data of the user in the class verification period in case that the class verification period is detected to expire.

For example, after the merchant registers, the user can pay for the commodity sold by the merchant through the payment application, the merchant can pay for other parties based on the payment application, both of the two types of transaction behaviors belong to the merchant, and under the condition that the transaction behavior of the merchant is detected for the first time, the specific time interval is 3 months, the type verification period of the merchant is determined by taking the transaction time of the transaction behavior as the period starting point and the time after 3 months as the period ending point; in the event that the arrival of the cycle end of the class verification cycle is detected, the expiration of the class verification cycle is determined.

It should be noted that, in order to save the resources of the category verification, the specific time interval for determining the first category verification period after the registration of the merchant may be different from the specific time interval for subsequently determining the category verification period; for example, after registering, the merchant determines that the specific time interval of the first category verification period is 3 months, and subsequently determines that the specific time interval of each category verification period is 6 months; here, whether the specific time interval for determining the first category verification period is the same as the specific time interval for subsequently determining the category verification period may be configured according to an actual scenario, which is not limited herein. It should be noted that, each category verification period is a period starting point of the transaction time of the first transaction behavior after the end of the category verification period.

In the registering process of the merchant, in addition to the recommendation of the category of the merchant to the merchant, the merchant may submit the category of the merchant, and in order to ensure the accuracy of the category of the merchant submitted by the merchant, in an alternative implementation provided in this embodiment, the following operations are performed:

acquiring the merchant data submitted by the merchant and the class of the merchant to be verified, and carrying out class verification on the class of the merchant to be verified based on the merchant data;

And taking the class of the merchant to be verified as the class of the merchant under the condition that class verification passes.

Specifically, in the process of registering the merchant, after acquiring the merchant data submitted by the merchant and the class of the merchant to be checked, in order to ensure the accuracy of the class of the merchant to be checked submitted by the user, the class of the merchant to be checked is checked based on the merchant data, and the class of the merchant to be checked is taken as the class of the merchant under the condition that the class check passes; if the category verification fails, determining a recommended merchant category based on the business voucher contained in the merchant data, and determining the recommended merchant category as the merchant category of the merchant according to a confirmation instruction of the merchant to the recommended merchant category.

In an optional implementation manner provided in this embodiment, in a process of performing category verification on a category of a merchant to be verified, the following operations are performed:

reading an operation range recorded in an operation certificate contained in the merchant data;

checking whether the class of the merchant to be checked is in the operating range;

if yes, determining that the category verification passes; if not, determining that the category verification fails.

For example, the merchant name on the business license included in the merchant data is "xxx food limited liability company", and the business scope in the business license includes: sales: vegetables, fruits, artwork, cosmetics; the class of the merchant to be verified submitted by the merchant is cosmetic manufacture, and the cosmetic manufacture is verified to be not in the business range of the business license of the merchant, so that the class verification is determined to be failed.

The method for determining the category of the merchant in the registration process of the two merchants is provided, and the two methods can exist independently or can be combined;

for example, acquiring merchant data submitted by the merchant, and determining a recommended merchant category based on the business voucher contained in the merchant data;

transmitting recommendation information of the recommendation merchant category to the merchant;

if a confirmation instruction of the recommended merchant category by the merchant is detected, determining the recommended merchant category as the merchant category of the merchant;

if the class of the to-be-verified merchant submitted by the merchant based on the recommended information is detected, carrying out class verification on the class of the to-be-verified merchant based on the merchant data, and taking the class of the to-be-verified merchant as the class of the merchant under the condition that the class verification passes;

and if the category verification fails, sending a verification result that the category verification fails to pass to the merchant.

For another example, the merchant data submitted by the merchant and the class of the merchant to be verified are obtained, and class verification is carried out on the class of the merchant to be verified based on the merchant data;

if the class verification is passed, the class of the merchant to be verified is used as the class of the merchant;

If the category verification fails, determining a recommended merchant category based on the business voucher contained in the merchant data; and determining the recommended merchant category as the merchant category of the merchant according to the confirmation instruction of the merchant to the recommended merchant category.

In addition, other forms of combination may be performed, and this embodiment will not be described in detail here.

Step S204, determining a target merchant category based on the merchant data and the transaction data, and checking whether the target merchant category is the same as the merchant category of the merchant.

In the step, under the condition that the expiration of the category verification period is detected, transaction data of the merchant in the category verification period is obtained, in the step, a target merchant category is determined based on the merchant data and the transaction data, whether the target merchant category is the same as the merchant category of the merchant is verified, and if yes, no processing is performed; if not, the following step S206 is executed, and the merchant category is updated to the target merchant category according to the confirmation instruction of the merchant to the target merchant category.

The target merchant category includes the determined actual merchant category of the merchant.

In this embodiment, the accuracy of the merchant category of the merchant is checked by checking the target merchant category and the merchant category of the merchant determined based on the merchant data and the transaction data, so as to ensure that the commodity or service actually managed by the merchant is matched with the merchant category of the merchant.

When the method is implemented, after transaction data of the merchant in a category verification period is obtained, determining the actual merchant category based on the transaction data; after determining the actual merchant category, checking whether the actual merchant category is in the business scope of the merchant, so as to avoid the out-of-scope business of the merchant and promote the effectiveness of business of the merchant; in an optional implementation manner provided in this embodiment, in a process of determining a target merchant category based on merchant data and transaction data, the following operations are performed:

determining an actual merchant category based on the transaction data;

verifying whether the actual merchant category is in the business scope recorded in the business voucher contained in the merchant data;

if yes, determining the actual merchant category as the target merchant category;

if not, based on the operation range and the actual merchant category, sending a category abnormality reminder to the merchant; if the supplementary merchant data submitted by the merchant based on the class anomaly reminding is detected, carrying out class verification on the actual merchant class based on the supplementary merchant data; and determining the actual merchant category as the target merchant category if category verification passes.

Specifically, firstly determining an actual merchant category based on transaction data, verifying whether the actual merchant category is in an operation range recorded in an operation voucher included in merchant data in order to ensure that the merchant operates according to the operation range agreed by the operation voucher, if so, determining the actual merchant category as a target merchant category, if not, prompting the merchant to supplement merchant data to prove that the actual merchant category of the merchant belongs to the operation range agreed by the user, otherwise, prompting the merchant to supplement the merchant data;

in the process of reminding a merchant to supplement merchant data, in order to promote the perception degree of the merchant to the actual merchant category, based on the actual merchant category and the business scope of the merchant, sending a category abnormality reminder to the merchant, if the supplementary merchant data submitted by the merchant based on the category abnormality reminder is detected, carrying out category verification on the actual merchant category based on the supplementary merchant data, and determining the actual merchant category as a target merchant category under the condition that the category verification is passed; if the supplementary merchant data submitted by the merchant based on the class anomaly reminding is not detected or class verification is not passed, the transaction behavior of the merchant can be limited to avoid that the merchant does not influence the management effect according to the agreed business of the business voucher.

It should be noted that, the supplementary merchant data may be merchant data that is submitted by the merchant for the actual merchant category; such as supplementary business vouchers; the process of verifying the category of the actual merchant based on the supplementary merchant data is similar to the process of verifying the category of the merchant based on the merchant data, and the embodiment is not limited herein, but only needs to refer to the related content.

Taking the merchant category of the merchant as food sales as an example, after transaction data in a category verification period of the merchant is acquired, firstly determining that the actual merchant category is cosmetic sales based on the transaction data, and then verifying whether the cosmetic sales are in the business scope of the merchant: sales: and in vegetables, fruits, artworks and cosmetics, the cosmetics are checked to be in the business scope of merchants, and the sales of the cosmetics is determined as the category of target merchants.

For another example, after transaction data in a class verification period of the merchant is obtained, determining that the actual merchant class is clothing sales based on the transaction data, and after verification, the clothing sales unit is in the business scope of the merchant, and generating a business scope including: sales: vegetables, fruits, artwork, cosmetics; actual merchant category: and (3) carrying out abnormal class reminding on clothing sales so as to remind a merchant of supplementing business vouchers related to service sales, and if supplementing merchant data corresponding to the actual merchant class of the merchant supplementation is detected, determining the actual merchant class service sales as a target merchant class.

In an alternative implementation manner of determining an actual merchant category based on transaction data provided in this embodiment, the following operations are performed:

determining at least one candidate merchant category based on a transaction amount contained in the transaction data;

and determining a candidate merchant category matched with the transaction environment data contained in the transaction data as the actual merchant category in the at least one candidate merchant category.

The transaction environment data can be an environment image collected by the payment sign display equipment or an environment image collected by the collection sign collecting equipment in the collection sign collecting process.

In determining the actual merchant category based on the transaction data, in the case where the transaction data includes the transaction amount and the transaction environment data, at least one candidate merchant category is first determined based on the transaction amount included in the transaction data, and then, among the at least one candidate merchant category, a candidate merchant category matching the transaction environment data is determined as the actual merchant category. That is, at least one candidate merchant category matching the transaction amount interval with the transaction amount included in the transaction data is screened out from the candidate merchant category set, and then the candidate merchant category matching the transaction environment data is determined as the actual merchant category from the at least one candidate merchant category.

For example, the transaction data includes data of 3 transaction behaviors, wherein transaction amounts include m1, m2 and m3, at least one candidate merchant category including m1, m2 and m3 in a transaction amount interval is screened out in a candidate merchant category set, at least one candidate merchant category including clothing sales and cosmetic sales is obtained, a transaction environment image in the transaction data is identified, environmental features corresponding to the transaction environment image are obtained as clothing, and clothing sales in the candidate merchant category is determined as an actual merchant category.

It should be noted that, the above description is only about the process of determining the actual merchant category according to the transaction amount and the transaction environment data in the transaction data, and other data, such as order information of the transaction order, may be also included in the transaction data; the determination of the actual merchant category may also be made based on the transaction amount, transaction context data, and/or other data in the transaction data, e.g., determining the actual merchant category from order information of the transaction order; specifically, reading commodity names in the order information, and determining actual merchant categories based on the commodity names; such as the trade name "xxx knitwear" in the order information, the corresponding actual business category is determined to be the clothing category. The commodity name or the corresponding relation between the keywords in the commodity name and the actual merchant category can be configured in advance.

In order to avoid creating a trade order by a merchant through false commodity names, in this embodiment, the actual commodity category determined based on the order information may be checked based on the trade environment data, and whether the actual commodity category determined based on the order information is matched with the trade environment data is checked, if so, the actual commodity category is determined to be valid; if not, carrying out matching verification on the determined actual commodity category based on other data in the transaction data; for example, after determining an actual merchant category according to order information of a transaction order, checking whether transaction environment data in transaction data is matched with environment data corresponding to the actual merchant category, if so, checking whether the actual merchant category is in a business scope of a merchant; if not, checking whether the transaction amount in the transaction data is matched with the transaction amount corresponding to the actual merchant category, and if so, checking whether the actual merchant category is in the business range of the merchant; if not, a determination of the actual merchant category may be made based on the transaction amount, transaction context data, and/or other data. The determination manner of the actual merchant category is not particularly limited in this embodiment.

In the implementation, after determining the target merchant category based on the merchant data and the transaction data, checking whether the target merchant category is the same as the merchant category of the merchant; if yes, the method is not carried out; if not, go to step S206.

In addition, step S204 may be replaced by determining a target merchant category based on the transaction data, checking whether the target merchant category is the same as the merchant category of the merchant, and forming a new implementation with other processing steps provided in this embodiment. Optionally, after determining the target merchant category based on the transaction data, further comprising: checking whether the target merchant category is in an operation range recorded in operation certificates contained in merchant data of the merchants, if so, executing the operation of checking whether the target merchant category is the same as the merchant category of the merchants, and if not, sending a category abnormality reminder to the merchants based on the operation range and the actual merchant category; if the supplementary merchant data submitted by the merchant based on the class anomaly reminding is detected, carrying out class verification on the actual merchant class based on the supplementary merchant data; and determining the actual merchant category as the target merchant category if category verification passes.

And step S206, updating the merchant category to the target merchant category according to the confirmation instruction of the merchant to the target merchant category.

In the case that the target merchant category determined based on the transaction data of the merchant and the merchant data is different from the merchant category of the merchant, in order to ensure the validity of the recorded merchant category, the merchant category of the merchant is updated to the target merchant category; in order to ensure the validity of the merchant category of the merchant, before updating the merchant category of the merchant to the target merchant category, the target merchant category is confirmed by the merchant, that is, the merchant category is updated to the target merchant category according to the confirmation instruction of the merchant to the target merchant category, so as to ensure the accuracy of the recorded merchant category of the merchant.

In this embodiment, the merchant category of the merchant refers to the merchant category determined after registration of the merchant or the merchant category determined and updated in the previous category verification period of the category verification period; the target merchant category determined in the embodiment comprises a merchant category determined according to the merchant data and the transaction data of the category verification period, and the target merchant category is compared with the target merchant category of the next category verification period as the merchant category of the merchant after being confirmed by the merchant.

In addition, step S206 may be replaced by updating the merchant category to the target merchant category, and forming a new implementation together with other processing steps provided in the present embodiment.

Step S208, constructing service labels of the merchants according to the target merchant categories so as to perform service processing according to the service labels.

The service tag comprises a tag which is created and used for representing a target merchant category of a merchant; the service tag in the embodiment can be a business image representing the category of business; for example, "merchant a is a chain convenience store" and "merchant B is a food sales mall". The service processing comprises processing by taking a merchant as a service object; for example, verification processing of rights and interests for the merchant, extraction processing of processing fees for transactions for the merchant, recommendation processing for the merchant, and the like.

Specifically, after the service label of the merchant is constructed according to the category of the target merchant, the target application performs rights and interests on the merchant in one dimension, so that more effective rights and interests can be released according to the category of the target merchant of the merchant, and rights and interests verification and verification can be further realized; in the other dimension, the target merchant category is used as an influence factor of the target application on the determination of the transaction processing cost of the merchant, so that more accurate calculation of the transaction processing cost is realized, and in the other dimension, in order to improve the perception degree of the merchant on the target application, recommendation processing can be performed on the merchant based on the target merchant category of the merchant. The procedure of service processing in these three dimensions is specifically described below.

(1) Rights and interests verifying pin

In an optional implementation manner provided in this embodiment, during a service processing process according to a service tag, the following operations are performed:

if the transaction request of the merchant is detected, reading a target interest matched with the service tag;

and carrying out transaction processing on the transaction request based on the target rights and the service tag.

Optionally, the transaction request may be a transaction request using a merchant as a resource transfer-in party, or may be a transaction request using a merchant as a resource transfer-out party. The target equity refers to equity to be revoked of a target merchant category in a service tag included in a revoked range. If the read target equity includes a plurality of target equities, a target equity is determined according to the issuing time, the remaining period and/or equity amount are verified; alternatively, multiple target benefits are commonly used without restriction between target benefits that cannot be used simultaneously.

Specifically, under the condition that the transaction request of the merchant is detected, the target interests matched with the service tags of the merchant are read, and then the transaction request is processed based on the target interests and the service tags.

For example, the merchant representation is a cosmetic sales merchant; after a transaction request of a user for commodity of the merchant is obtained, the merchant portrait of the merchant is read, a target equity suitable for cosmetic verification is determined in equity to be verified, an actual transaction amount is calculated based on the target equity and the transaction amount in the transaction request, and transaction processing is performed based on the actual transaction amount.

In order to calculate the accurate processing amount during the transaction processing, in an alternative implementation manner provided in this embodiment, based on the target equity and the service tag, the transaction processing on the transaction request is implemented in the following manner:

calculating the actual transaction amount of the transaction request according to the target equity and the transaction amount contained in the transaction request;

calculating a processing amount corresponding to the actual transaction amount based on the service tag;

transferring the processing funds corresponding to the processing amount in the transaction funds to an intermediate account, and transferring the transaction amount except the processing funds in the transaction funds to a merchant account.

Specifically, determining a processing amount corresponding to the actual transaction amount according to a processing proportion corresponding to the service tag, and deducting the commission according to the processing amount; for example, if the processing proportion of the cosmetic sales is a%, and the calculated actual transaction amount is m4, the calculated processing amount is m4×a%, m4×a% of the transaction funds are transferred to the intermediate account corresponding to the target application, and m4-m4×a% of the transaction funds are transferred to the merchant account.

In addition, the actual transaction amount of the transaction request can be calculated according to the target equity and the transaction amount contained in the transaction request;

calculating the processing amount corresponding to the transaction request based on the service tag;

transferring the processing funds corresponding to the processing amount in the transaction funds of the actual transaction amount to an intermediate account, and transferring the transaction amount except the processing funds in the transaction funds to a merchant account.

That is, the processing amount is not determined in proportion to the actual transaction amount, and the fee deduction is performed only in accordance with the processing amount corresponding to the service tag. For example, if the actual transaction amount is m4 and the processing amount corresponding to the transaction request of the cosmetic sales is m5, transferring the funds of m5 in the transaction funds to the intermediate account corresponding to the target application, and transferring the funds of m4-m5 to the merchant account.

(2) Processing cost determination

if the transaction request of the merchant is detected, calculating the processing amount of the transaction request based on the service tag and the transaction amount carried in the transaction request;

Transferring the processing funds corresponding to the processing amount in the transaction funds to an intermediate account, and transferring the transaction funds except the processing funds in the transaction funds to a merchant account;

or,

if the transaction request of the merchant is detected, calculating the processing amount of the transaction request based on the service tag;

transferring the processing funds corresponding to the processing amount in the transaction funds to an intermediate account, and transferring the transaction funds except the processing funds in the transaction funds to a merchant account.

It should be noted that, the determination of the processing cost is similar to the above-mentioned related content, and the description of this embodiment is omitted here.

(3) Recommendation processing

In an optional implementation manner provided in this embodiment, after the service tag of the merchant is constructed, the following operations may be further performed:

determining interaction recommendation merchants of the merchants based on the service tags;

and sending the service label and the merchant identification of the interaction recommendation merchant to the merchant so as to enable the merchant to perform service interaction with the interaction recommendation merchant.

In the specific execution process, based on the service label, the merchant is subjected to interactive recommendation, so that the merchant can be subjected to service interaction based on the recommended interactive recommendation merchant.

For example, if the merchant representation is a cosmetic sales merchant, the merchant determines that the service label is an interactive recommendation merchant of the cosmetic manufacturing merchant according to the merchant representation, and sends the merchant identification of the interactive recommendation merchant to the merchant, so that the merchant can purchase the cosmetic based on the interactive recommendation merchant.

In addition, the interactive recommendation user of the merchant can be determined, specifically, based on the service tag, the interactive recommendation user of the merchant is determined, and the service tag and the user identification of the interactive recommendation user are sent to the merchant, so that the merchant can conduct commodity recommendation to the interactive recommendation user.

For example, in a process of recommending a merchant whose merchant representation is a cosmetic sales merchant, a user whose consumption preference includes cosmetic consumption is determined as an interactive recommendation user of the merchant to recommend to the merchant according to the merchant representation.

It should be noted that, the interaction recommendation merchant and the interaction recommendation user can be combined to recommend to the merchant; specifically, based on the service tag, determining an interaction recommendation merchant and an interaction recommendation user of the merchant; and sending the service tag, the merchant identification of the interaction recommendation merchant and the user identification of the interaction recommendation user to the merchant so that the merchant performs service interaction with the interaction recommendation merchant and the interaction recommendation user.

After the service label of the merchant is constructed, the service label is stored on one hand so as to carry out service processing of the merchant according to the service label, and on the other hand, the service label can be sent to the merchant so that the merchant can carry out related operation according to the service label.

In summary, in the method for processing the category of the merchant provided in this embodiment, in the process of registering the merchant, the category of the merchant is recommended according to the merchant data provided by the merchant, the merchant does not need to manually select the category of the merchant, the risk of a selection error caused by manually selecting the category of the merchant is reduced, further, the target category of the merchant is confirmed according to the transaction data in the category verification period, and when the target category of the merchant is different from the category of the merchant, the target category of the merchant is updated to the category of the merchant after the target category of the merchant is confirmed, so as to ensure the validity and accuracy of the category of the merchant, and finally, marketing or recommendation activities are performed based on accurate and effective user images in a manner of performing the image based on the target category of the merchant, thereby improving the perception degree of the merchant.

The following further describes the method for processing the category of the merchant provided in this embodiment with reference to fig. 3 and fig. 4 by taking an example of application of the method for processing the category of the merchant in the scene of business operation provided in this embodiment, and referring to fig. 4, the method for processing the category of the merchant applied in the scene of business operation specifically includes the following steps.

As shown in fig. 3, the merchant submits merchant data to the server, the server determines recommended business categories according to the merchant data and recommends the recommended business categories to the merchant, and determines the business categories as business categories of the merchant according to a confirmation instruction of the merchant for the recommended business categories; and under the condition that the first transaction behavior of the user to the merchant is detected, determining a category verification period, and under the condition that the category verification period is detected to be reached, verifying whether the target business category determined according to the transaction data of the merchant in the category verification period is the same as the business category of the merchant, if so, continuing to transact the merchant, otherwise, updating the business category of the merchant into the target business category, and constructing a merchant image of the target business category, so as to perform service processing in two dimensions of the merchant and in the target application based on the merchant image.

Step S402, acquiring merchant data of a merchant.

Step S404, based on the business voucher contained in the merchant data, the recommended business category is determined and sent to the merchant.

Step S406, according to the confirmation instruction of the merchant for the recommended business category, the recommended business category is determined as the business category of the merchant.

The business category in this embodiment includes a merchant category code.

In step S408, in the case where the first transaction behavior of the merchant is detected, a category verification period of the merchant is determined based on the transaction time of the first transaction behavior and the specific time interval.

Step S410, if the category verification period is detected to be expired, transaction data of transaction behaviors of the merchant in the category verification period is obtained, and the target business category is determined based on the transaction data.

Step S412, checking whether the target business category is the same as the business category of the merchant when the target business category is in the business scope of the business document record;

if yes, the method is not carried out;

if not, go to step S414 to step S416.

Step S414, sending a category change reminder containing the target business category to the merchant, and updating the business category of the merchant into the target business category according to a confirmation instruction of the merchant to the target business category.

Step S416, constructing business images of business management categories according to the target management categories, so as to perform service processing according to the business images.

One or more embodiments of a merchant category processing device provided herein are as follows:

in the foregoing embodiments, a method for processing a class of merchants is provided, and a device for processing a class of merchants is provided correspondingly, which are described below with reference to the accompanying drawings.

Referring to fig. 5, a schematic diagram of an embodiment of a merchant category processing device according to the present embodiment is shown.

Since the apparatus embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions should be referred to the corresponding descriptions of the method embodiments provided above. The device embodiments described below are merely illustrative.

The embodiment provides a merchant category processing device, which comprises:

a data acquisition module 502 configured to acquire transaction data for a merchant over a category verification period;

a category verification module 504 configured to determine a target merchant category based on merchant data and the transaction data and verify whether the target merchant category is the same as the merchant category of the merchant;

if not, a category updating module 506 is operated, and the category updating module 506 is configured to update the merchant category to the target merchant category according to a confirmation instruction of the merchant to the target merchant category;

the tag construction module 508 is configured to construct a service tag of the merchant according to the target merchant category, so as to perform service processing according to the service tag.

Corresponding to the above-described method for processing a class of merchants, one or more embodiments of the present disclosure further provide a device for processing a class of merchants, where the device is configured to execute the method for processing a class of merchants provided above, and fig. 6 is a schematic structural diagram of the device for processing a class of merchants provided by the one or more embodiments of the present disclosure.

The merchant category processing device provided in this embodiment includes:

as shown in FIG. 6, merchant category processing devices may vary considerably in configuration or performance, and may include one or more processors 601 and memory 602, where memory 602 may store one or more stored applications or data. Wherein the memory 602 may be transient storage or persistent storage. The application program stored in memory 602 may include one or more modules (not shown in the figures), each of which may include a series of computer-executable instructions in the merchant category processing device. Still further, the processor 601 may be configured to communicate with the memory 602 and execute a series of computer executable instructions in the memory 602 on the merchant category processing device. The merchant category processing device may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input/output interfaces 605, one or more keyboards 606, and the like.

In one particular embodiment, a merchant category processing device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the merchant category processing device, and configured to be executed by one or more processors, the one or more programs including computer-executable instructions for:

acquiring transaction data of a merchant in a category verification period;

determining a target merchant category based on merchant data and the transaction data, and verifying whether the target merchant category is the same as the merchant category of the merchant;

if not, updating the merchant category into the target merchant category according to the confirmation instruction of the merchant to the target merchant category;

and constructing a service label of the merchant according to the target merchant category so as to perform service processing according to the service label.

One or more embodiments of a storage medium provided in the present specification are as follows:

corresponding to the above-described merchant category processing method, one or more embodiments of the present disclosure further provide a storage medium based on the same technical concept.

The storage medium provided in this embodiment is configured to store computer executable instructions that, when executed by a processor, implement the following flow:

acquiring transaction data of a merchant in a category verification period;

It should be noted that, in the present specification, the embodiment about the storage medium and the embodiment about the merchant category processing method in the present specification are based on the same inventive concept, so that the specific implementation of the embodiment may refer to the implementation of the corresponding method, and the repetition is omitted.

In this specification, each embodiment is described in a progressive manner, and the same or similar parts of each embodiment are referred to each other, and each embodiment focuses on the differences from other embodiments, for example, an apparatus embodiment, and a storage medium embodiment, which are all similar to a method embodiment, so that description is relatively simple, and relevant content in reading apparatus embodiments, and storage medium embodiments is referred to the part description of the method embodiment.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can 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 are also possible or may be advantageous.

In the 30 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each unit may be implemented in the same piece or pieces of software and/or hardware when implementing the embodiments of the present specification.

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

The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

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 one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

One or more embodiments of the present specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing description is by way of example only and is not intended to limit the present disclosure. Various modifications and changes may occur to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. that fall within the spirit and principles of the present document are intended to be included within the scope of the claims of the present document.

Claims

1. A method for merchant category processing, comprising:

acquiring transaction data of a merchant in a category verification period;

2. The merchant category processing method as set forth in claim 1, wherein the step of acquiring transaction data of the merchant during the category verification period is performed further comprising:

3. The method of merchant category processing according to claim 1, the determining a target merchant category based on merchant data and the transaction data, comprising:

determining an actual merchant category based on the transaction data;

if yes, determining the actual merchant category as the target merchant category.

4. The merchant category processing method of claim 3, wherein if the verification that the actual merchant category is in the business scope operation recorded in the business voucher included in the merchant data is no, the following operations are executed:

Based on the operating range and the actual merchant category, sending a category abnormality reminder to the merchant;

if the supplementary merchant data submitted by the merchant based on the class anomaly reminding is detected, carrying out class verification on the actual merchant class based on the supplementary merchant data;

and determining the actual merchant category as the target merchant category if category verification passes.

5. A method of merchant category processing according to claim 3, the determining an actual merchant category based on the transaction data comprising:

6. The method for processing a class of merchants according to claim 1, wherein the service processing according to the service tag comprises:

7. The merchant category processing method of claim 6, wherein the transaction processing the transaction request based on the target equity and the service tag comprises:

8. The method for processing a class of merchants according to claim 1, further comprising, after the operation of constructing the service tag of the merchant according to the target class of merchants:

9. The method for processing a category of a merchant according to claim 2, wherein after the step of determining the recommended category of the merchant as the category of the merchant according to the confirmation instruction of the user for the recommended category of the merchant is performed, further comprising:

and if the class verification period is detected to be expired, executing the step of acquiring transaction data of the merchant in the class verification period.

10. The method for processing a class of merchants according to claim 1, wherein the step of acquiring transaction data of the class verification period is performed by the merchant, further comprising:

11. A merchant category processing device comprising:

the data acquisition module is configured to acquire transaction data of merchants in a category verification period;

a category verification module configured to determine a target merchant category based on merchant data and the transaction data and verify whether the target merchant category is the same as a merchant category of the merchant;

if not, a class updating module is operated, and the class updating module is configured to update the class of the merchant to the class of the target merchant according to a confirmation instruction of the merchant to the class of the target merchant;

And the label construction module is configured to construct a service label of the merchant according to the target merchant category so as to perform service processing according to the service label.

12. A merchant category processing device comprising:

a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:

acquiring transaction data of a merchant in a category verification period;

13. A storage medium storing computer-executable instructions that when executed by a processor implement the following:

acquiring transaction data of a merchant in a category verification period;