CN117611172A

CN117611172A - Merchant order receiving method, device, equipment and storage medium based on intelligent contract

Info

Publication number: CN117611172A
Application number: CN202311599918.8A
Authority: CN
Inventors: 丁颖; 方嘉慈; 左杰文; 刘子伦
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-11-27
Filing date: 2023-11-27
Publication date: 2024-02-27

Abstract

The application provides a merchant order receiving method, device, equipment and storage medium based on intelligent contracts, and relates to the technical field of big data, the technical field of finance and technology or other relevant fields. The method comprises the following steps: responding to a merchant profiling instruction of a target merchant, and acquiring merchant profile information corresponding to the target merchant; based on merchant profile information, establishing a merchant profile corresponding to a target merchant, and establishing a corresponding sub-account for the target merchant under a parent account corresponding to a service platform to which the target merchant belongs; creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the merchant profile information; and after determining that the transaction order payment aiming at the target merchant is completed, invoking a merchant order-receiving intelligent contract, and performing clearing settlement processing on the transaction order to obtain a merchant settlement result. The method can enable the merchant to view settlement data in real time, increase transparency of fund data and improve safety of fund links.

Description

Merchant order receiving method, device, equipment and storage medium based on intelligent contract

Technical Field

The present disclosure relates to the field of big data, the field of financial science and technology, and more particularly, to a method, an apparatus, a device, and a storage medium for acquiring a merchant order based on an intelligent contract.

Background

At present, when a merchant receives a bill, the funds to be settled of a customer are temporarily stored in a public settlement hanging account, and then different branches are controlled by a control program according to preset settlement period, billing rate, settlement account and other parameter information so as to settle the funds to be settled to a service platform, the merchant and the like.

The merchant order receiving mode enables the to-be-settled funds corresponding to the service platform and the merchant to be stored in a public clearing and settlement hanging account, so that effective separation of the to-be-settled funds cannot be realized, and the service platform and the merchant cannot respectively and independently inquire the to-be-settled funds. In addition, in the above embodiment, there is no forced constraint on the funds link of the merchant for acquiring the order, so that a certain potential safety hazard exists in the funds link.

Disclosure of Invention

The application provides a merchant order receiving method, device, equipment and storage medium based on intelligent contracts, which are used for solving the technical problems that in the prior art, a service platform or a merchant cannot check respective funds to be settled in real time, and a fund settlement link has a certain security risk.

In a first aspect, the present application provides a merchant acquiring method based on an intelligent contract, including:

Responding to a merchant profiling instruction of a target merchant, and acquiring merchant profile information corresponding to the target merchant; wherein, the merchant archive information comprises configuration information of merchant receipts;

based on the merchant profile information, establishing a merchant profile corresponding to the target merchant, and establishing a corresponding sub-account for the target merchant under a parent account corresponding to a service platform to which the target merchant belongs; the parent account is used for recording data to be settled corresponding to the service platform; the sub-account is used for recording data to be settled corresponding to the target merchant;

creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the merchant profile information; the merchant order-receiving intelligent contract is used for carrying out clearing settlement processing on the target merchant;

and after determining that the transaction order payment aiming at the target merchant is completed, calling the merchant order-receiving intelligent contract, and performing clearing settlement processing on the transaction order to obtain a merchant settlement result.

In one example, under a parent account corresponding to a service platform to which the target merchant belongs, creating a corresponding child account for the target merchant includes:

Determining each primary account included under a parent account corresponding to a service platform to which the target merchant belongs; wherein the primary account characterizes an account that has been created under the parent account;

if the primary account matched with the target merchant is not determined from the primary accounts, creating a corresponding sub-account for the target merchant under the parent account corresponding to the service platform to which the target merchant belongs.

In one example, the configuration information of the merchant acquirer includes template selection information and settlement parameter information; the creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the merchant profile information comprises the following steps:

determining an intelligent contract template matched with the target merchant from an intelligent contract library based on the template selection information; the template selection information comprises industry information of the industry to which the target merchant belongs;

creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the settlement parameter information and the intelligent contract template; wherein the settlement parameter information indicates at least the following information: directional wetting rules, settlement period and settlement mode; and the settlement mode characterizes a settlement account corresponding to the target merchant.

In one example, the clearing settlement process includes a data clearing process and a data settlement process; the step of calling the merchant order-receiving intelligent contract, and performing clear settlement processing on the transaction order to obtain a merchant settlement result, which comprises the following steps:

invoking the merchant order-receiving intelligent contract, and performing the wetting treatment on the payment amount corresponding to the transaction order based on the directional wetting rule in the merchant order-receiving intelligent contract to obtain the residual amount after the wetting treatment;

recording the residual amount after the sorting treatment into a sub-account corresponding to the target merchant, and finishing the data sorting treatment of the transaction order to obtain a data sorting result;

based on the settlement period and the settlement mode in the merchant order-receiving intelligent contract, carrying out data settlement processing on the data to be settled recorded in the sub-account corresponding to the target merchant to obtain a data settlement result;

and determining the merchant settlement result based on the data clearing result and the data settlement result.

In one example, after recording the remaining amount after the moisturizing process into the sub-account corresponding to the target merchant, the method further includes:

Responding to a query instruction of the target merchant for the first target settlement data, and determining and displaying data detail information of the data to be settled in the sub-account corresponding to the target merchant; wherein the first target settlement data characterizes data to be settled of the target merchant.

In one example, the method further comprises:

responding to the query operation of the service platform on the second target settlement data, and determining and displaying the data detail information of the to-be-settled data in the target account matched with the second target settlement data in the service platform; the second target settlement data represents to-be-settled data of the service platform or represents to-be-settled data of a merchant under the service platform.

In one example, the method further comprises:

responding to the modification operation of the merchant profile information of the target merchant, and acquiring modified merchant profile information;

and creating a new merchant order-receiving intelligent contract corresponding to the target merchant based on the modified merchant archive information, and performing clear settlement processing on the transaction order based on the new merchant order-receiving intelligent contract corresponding to the target merchant to obtain a merchant settlement result.

In a second aspect, the present application provides a merchant acquiring device based on an intelligent contract, including:

the response unit is used for responding to the merchant profiling instruction of the target merchant and acquiring merchant profile information corresponding to the target merchant; wherein, the merchant archive information comprises configuration information of merchant receipts;

the first creating unit is used for creating a merchant file corresponding to the target merchant based on the merchant file information and creating a corresponding sub-account for the target merchant under a parent account corresponding to a service platform to which the target merchant belongs; the parent account is used for recording data to be settled corresponding to the service platform; the sub-account is used for recording data to be settled corresponding to the target merchant;

the second creating unit is used for creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the merchant profile information; the merchant order-receiving intelligent contract is used for carrying out clearing settlement processing on the target merchant;

and the processing unit is used for calling the merchant order-receiving intelligent contract after determining that the transaction order payment aiming at the target merchant is completed, and performing clear settlement processing on the transaction order to obtain a merchant settlement result.

In one example, the first creating unit is configured to:

In one example, the configuration information of the merchant order includes template selection information and settlement parameter information, and at this time, the second creating unit is configured to:

In one example, the clearing settlement processing includes a data clearing processing and a data settlement processing, and at this time, the processing unit is configured to:

In one example, the apparatus further comprises: the first query unit is used for determining and displaying the data detail information of the data to be settled in the sub-account corresponding to the target merchant in response to the query instruction of the target merchant for the first target settlement data after recording the residual amount after the moisturizing treatment into the sub-account corresponding to the target merchant; wherein the first target settlement data characterizes data to be settled of the target merchant.

In one example, the apparatus further comprises: the second query unit is used for responding to the query operation of the service platform on the second target settlement data, and determining and displaying the data detail information of the data to be settled in the target account matched with the second target settlement data in the service platform; the second target settlement data represents to-be-settled data of the service platform or represents to-be-settled data of a merchant under the service platform.

In one example, the apparatus further comprises: an updating unit, configured to obtain modified merchant profile information in response to a modification operation on the merchant profile information of the target merchant;

In a third aspect, the present application provides a computer device comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

The processor executes computer-executable instructions stored in the memory to implement the method of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions for performing the method of the first aspect when executed by a processor.

In a fifth aspect, the present application provides a computer program product comprising: computer-executable instructions stored in a readable storage medium from which at least one processor of a computer device can read, the at least one processor executing the computer-executable instructions causing the computer device to perform the method of the first aspect.

According to the intelligent contract-based merchant order receiving method, device, equipment and storage medium, merchant archive information corresponding to a target merchant can be obtained in response to a merchant filing instruction of the target merchant, merchant archives corresponding to the target merchant are built based on the merchant archive information, corresponding sub-accounts are built for the target merchant under a parent account corresponding to a service platform to which the target merchant belongs, at the moment, fund data of the target merchant can be clear and transparent, transparency of funds can be increased, and the target merchant can view fund conditions in real time through the sub-accounts. At this time, a merchant order-receiving intelligent contract corresponding to the target merchant can be created based on the merchant archive information, and after the transaction order payment for the target merchant is determined to be completed, the merchant order-receiving intelligent contract is called, and clear settlement processing is performed on the transaction order to obtain a merchant settlement result. At this time, the merchant order-receiving intelligent contract corresponding to the target merchant can be automatically created through the merchant file information, and the clear settlement processing flow of the target merchant is effectively prevented from being tampered through the merchant order-receiving intelligent contract, so that funds can be effectively prevented from being stolen, the safety and the reliability of a fund link are ensured, and the interests of all parties in the order-receiving process are further effectively maintained.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is a schematic flow chart of a merchant order receiving method based on intelligent contracts provided in the present application;

FIG. 2 is a flow chart of another method for acquiring merchant orders based on smart contracts provided in the present application;

fig. 3 is an application scenario schematic diagram of a merchant acquiring method based on an intelligent contract provided in the present application;

FIG. 4 is a schematic diagram of an application flow in response to a merchant profiling instruction for a target merchant provided by the present application;

FIG. 5 is a schematic diagram of an intelligent contract platform provided in the present application;

fig. 6 is a schematic flow chart of a clearing settlement process provided in the present application;

fig. 7 is a schematic flow chart of querying data to be settled by a target merchant;

FIG. 8 is a schematic diagram of a merchant acquiring device based on intelligent contracts according to the present application;

FIG. 9 is a schematic diagram of a merchant acquiring device based on an intelligent contract according to another embodiment of the present invention;

fig. 10 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

The term "and/or" is used herein to describe only one relationship, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist together, and B exists alone. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

It should be noted that, the merchant order receiving method, device, equipment and storage medium based on the intelligent contract provided by the application can be used in big data field, financial science and technology field or other related fields, and the application field of the merchant order receiving method, device, equipment and storage medium based on the intelligent contract provided by the application is not limited.

Intelligent contract: the system is a specific executable logic code corresponding to business activities, is a technical means provided for guaranteeing business contracts such as about execution, and in reality, is expressed as specific service clauses for clients to be served by merchants based on a bank-end intelligent contract technical system.

The merchant order receiving mode enables the to-be-settled funds corresponding to the service platform and the merchant to be recorded in the public settlement hanging account, so that effective separation of the to-be-settled funds cannot be realized, and the service platform and the merchant cannot respectively and independently inquire the to-be-settled funds. The merchant or the service platform cannot inquire the funds to be settled in real time before the receipt structure settles the funds to be settled to the merchant or the service platform, so that the use experience of the user is affected.

In addition, in the above embodiment, there is no forced constraint on the funds link of the merchant for acquiring the order, so that a certain potential safety hazard exists in the funds link.

The merchant order receiving method based on the intelligent contract aims to solve the technical problems in the prior art.

The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 1 is a flow chart of a merchant order receiving method based on an intelligent contract provided in the present application, as shown in fig. 1, the method includes:

S101, responding to a merchant profiling instruction of a target merchant, and acquiring merchant profile information corresponding to the target merchant.

The merchant archive information comprises configuration information of a merchant receipt.

In one example, the merchant profiling instruction is an instruction for creating a merchant profile corresponding to a target merchant and storing merchant profile information corresponding to the target merchant, where the merchant profiling instruction may be a profiling instruction initiated by the target merchant in a receipt structure or a package entering instruction initiated by a service platform for the target merchant.

In one example, the configuration information of the merchant receipt included in the merchant profile information may include basic attribute information of the target merchant and a settlement mode corresponding to the transaction funds, for example, the merchant profile information may include information of a merchant name of the target merchant, an industry to which the target merchant belongs, a payment mode set by the target merchant, a settlement period, a directional wetting rule, a directional settlement, and the like.

The method for acquiring the merchant acquiring list based on the intelligent contract provided by the embodiment of the application can be applied to an acquiring mechanism, and at the moment, after a server of the acquiring mechanism receives a merchant profiling instruction of a target merchant, the configuration information of the merchant acquiring list edited by the target merchant can be acquired to obtain merchant profile information corresponding to the target merchant.

S102, based on merchant profile information, establishing a merchant profile corresponding to the target merchant, and establishing a corresponding sub-account for the target merchant under a parent account corresponding to a service platform to which the target merchant belongs.

The parent account is used for recording data to be settled corresponding to the service platform; the sub-account is used for recording data to be settled corresponding to the target merchant.

In one example, the merchant profile may be used to determine the acquirer process (i.e., the clearing settlement process) corresponding to the target merchant.

In one example, a corresponding parent account may be set up for each service platform served by the acquirer, and a corresponding child account may be created under the parent account for the target merchant, where only a unique child account may be created under the parent account of the same service platform for the target merchant.

In one example, the number of service platforms to which the target merchant belongs may be plural, and in this case, the number of sub-accounts created for the target merchant may be plural.

S103, creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the merchant profile information.

The merchant order-receiving intelligent contract is used for carrying out clearing settlement processing on the target merchant.

In one example, a policy receiving process corresponding to the target merchant may be determined based on configuration information of a merchant policy receiving included in the merchant profile information, and a merchant policy receiving smart contract corresponding to the target merchant may be determined according to the policy receiving process.

S104, after the transaction order payment for the target merchant is determined to be completed, invoking a merchant order-receiving intelligent contract, and performing clearing settlement processing on the transaction order to obtain a merchant settlement result.

As can be seen from the above description, in the embodiment of the present application, merchant profile information corresponding to a target merchant may be obtained in response to a merchant profiling instruction for the target merchant, and a merchant profile corresponding to the target merchant may be established based on the merchant profile information, and a corresponding sub-account may be created for the target merchant under a parent account corresponding to a service platform to which the target merchant belongs. At this time, a merchant order-receiving intelligent contract corresponding to the target merchant can be created based on the merchant archive information, and after the transaction order payment for the target merchant is determined to be completed, the merchant order-receiving intelligent contract is called, and clear settlement processing is performed on the transaction order to obtain a merchant settlement result. At this time, the merchant order-receiving intelligent contract corresponding to the target merchant can be automatically created through the merchant file information, and the clear settlement processing flow of the target merchant is effectively prevented from being tampered through the merchant order-receiving intelligent contract, so that funds can be effectively prevented from being stolen, the safety and the reliability of a fund link are ensured, and the interests of all parties in the order-receiving process are further effectively maintained.

Fig. 2 is a flow chart of another method for acquiring a merchant order based on an intelligent contract provided in the present application, as shown in fig. 2, the method includes:

s201, responding to a merchant profiling instruction of a target merchant, and acquiring merchant profile information corresponding to the target merchant.

In an example, this step may be described in S101, which is not described in detail herein.

S202, establishing a merchant archive corresponding to the target merchant based on the merchant archive information.

S203, determining all primary accounts included under the parent account corresponding to the service platform to which the target merchant belongs.

Wherein the primary account characterizes an account that has been created under the parent account.

In one example, under the parent account corresponding to the service platform to which the target merchant belongs, each primary account included is associated with the merchant included under the service platform, and at this time, whether there is a primary account matched with the target merchant may be determined from each primary account under the parent account corresponding to the service platform to which the target merchant belongs. If it is determined that the primary accounts matched with the target merchants exist in the primary accounts under the parent accounts, the matched primary accounts can be determined to be sub-accounts corresponding to the target merchants.

In another example, if it is determined that there is no primary account matching the target merchant in each primary account under the parent account, the steps described below in S204 may be performed.

S204, if the primary account matched with the target merchant is not determined from the primary accounts, creating a corresponding sub-account for the target merchant under the parent account corresponding to the service platform to which the target merchant belongs.

The main account is used for recording data to be settled of all merchants contained in the service platform, and the sub account is used for recording data to be settled corresponding to the target merchant.

According to the embodiment, the service platform and each merchant under the service platform can be effectively isolated by the main account and the sub account, and the links of the data to be settled can be clearer and clearer, so that potential risks are avoided.

S205, creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the merchant profile information.

In one example, the configuration information of the merchant order may include template selection information and settlement parameter information, and at this time, a merchant order-receiving smart contract corresponding to the target merchant is created based on the merchant profile information, which specifically includes the following steps.

First, based on template selection information, an intelligent contract template matching the target merchant is determined from an intelligent contract library.

The template selection information comprises industry information of the industry to which the target merchant belongs. For example, the industry information of the industry to which the target merchant belongs may be a catering industry, a retail industry, a medical industry, etc., and the industry information of the industry to which the target merchant belongs is not particularly limited herein, so as to be able to be realized.

Then, based on the settlement parameter information and the intelligent contract template, a merchant order-receiving intelligent contract corresponding to the target merchant is created. Wherein the settlement parameter information indicates at least the following information: directional wetting rules, settlement period and settlement mode; the settlement mode represents a settlement account corresponding to the target merchant.

In one example, after the target merchant is documented, sub-accounts are created, and merchant order-receiving intelligent contracts are created, the target merchant may conduct business, at this time, the target merchant receives a payment request for a transaction order, and after the payment request is completed, it may be determined that payment for the transaction order of the target merchant is completed, and then, clearing settlement may be performed on the transaction order according to the steps described in S206 to S209 below, so as to obtain a merchant settlement result. The clearing settlement processing may include data clearing processing and data settlement processing.

In the embodiment, the merchant order-receiving intelligent contract corresponding to the target merchant can be automatically created according to the merchant archive information, so that the time is saved and the efficiency is improved.

S206, calling the merchant order-receiving intelligent contract, and based on the directional wetting rule in the merchant order-receiving intelligent contract, performing wetting treatment on the payment amount corresponding to the transaction order, so as to obtain the residual amount after the wetting treatment.

In one example, the directional wetting rule may include a wetting manner and a wetting party, and at this time, according to the wetting manner in the directional wetting rule, the payment amount corresponding to the transaction order may be subjected to wetting processing, and the wetting result may be checked into an account corresponding to each wetting party.

For example, the party may include an acquirer and/or a service platform, at which time the result of the moisture may be credited to an account corresponding to the acquirer and/or under a parent account corresponding to the service platform.

S207, recording the residual amount after the moisturizing treatment into a sub-account corresponding to the target merchant, and completing the data clearing treatment of the transaction order to obtain a data clearing result.

At this time, the data sorting result may represent the data to be settled corresponding to the target merchant.

S208, based on the settlement period and the settlement mode in the merchant order-receiving intelligent contract, carrying out data settlement processing on the data to be settled recorded in the sub-account corresponding to the target merchant, and obtaining a data settlement result.

In one example, after the data clearing result is obtained, it may be determined whether the data clearing requirement is met according to a clearing period included in the merchant order taking smart contract.

Under the condition that the data settlement requirement is met is determined, data settlement processing can be carried out on the data to be settled recorded in the sub-account corresponding to the target merchant according to the settlement mode in the merchant order-receiving intelligent contract, and a data settlement result is obtained.

And under the condition that the data settlement requirement is not met, ending the clearing settlement processing flow.

S209, determining a merchant settlement result based on the data sorting result and the data settlement result.

In the embodiment, the transaction order of the target merchant can be subjected to clearing settlement through the merchant order-receiving intelligent contract, so that the oriented wetting and oriented settlement of funds are realized, the safety and the accuracy of the funds are ensured, the funds can be effectively prevented from being stolen, and the rights and interests of the target merchant, the service platform and the order-receiving mechanism are further ensured.

In one example, after recording the remaining amount after the moisturizing process into the sub-account corresponding to the target merchant, the target merchant may query the corresponding data to be settled by querying the sub-account, and when implemented, may perform the steps described in S210 below.

S210, determining and displaying data detail information of the data to be settled in the sub-account corresponding to the target merchant in response to a query instruction of the target merchant for the first target settlement data.

The first target settlement data represent to-be-settled data of target merchants.

In one example, the data detail information of the data to be settled may include balance information corresponding to the sub-account, and in addition, the data detail information of the data to be settled may further include recording detail information of the sub-account, for example, the recording detail information may represent a specific value of the remaining amount after the moisturizing process, a recording time of the remaining amount after the moisturizing process, and the like.

In the embodiment, the target merchant can check the data to be settled in real time through the query instruction after the transaction order is completed, so that the target merchant can be helped to find the abnormal condition of the data to be settled in time, the data to be settled is monitored, the accuracy of the data to be settled is ensured, and unnecessary disputes can be avoided.

In another example, the embodiment of the application may further determine and display, in response to a query operation of the service platform on the second target settlement data, data detail information of the to-be-settled data in the target account matched with the second target settlement data in the service platform; the second target settlement data represents to-be-settled data of the service platform or to-be-settled data of a merchant under the service platform.

According to the embodiment, the service platform can check the data to be settled corresponding to the service platform in real time through the parent account, and check the data to be settled of all merchants under the service platform, namely funds to be settled through all primary accounts under the parent account, so that the service platform can optimize the layout strategy or the recommendation strategy and the like based on the data detail information of the data to be settled, and the service quality and the service performance of the service platform can be further improved.

In one example, after the order receipt rule (i.e., rule of clearing settlement processing) changes, the modified merchant profile information may be obtained in response to a modification operation of the merchant profile information of the target merchant, then a new merchant order receipt intelligent contract corresponding to the target merchant is created based on the modified merchant profile information, and clearing settlement processing is performed on the transaction order based on the new merchant order receipt intelligent contract corresponding to the target merchant, so as to obtain a merchant settlement result.

According to the embodiment, the change of the order receiving rule can be simply and quickly realized by modifying the file information of the merchant, the difficulty of updating the clearing settlement processing task is reduced, and the risk of updating the clearing settlement processing task is also reduced.

In one example, fig. 3 is an application scenario schematic diagram of a merchant order receiving method based on an intelligent contract provided in the present application. As shown in fig. 3, the application scenario includes: the system comprises an acquirer merchant management platform front end 301, an acquirer merchant management platform back end 302, a service platform 303, an intelligent contract platform 304, an acquirer order system 305 and an acquirer clearing and settling system 306.

The front end 301 of the acquirer merchant management platform is configured to create a merchant profile by calling the back end 302 of the acquirer merchant management platform, and set merchant profile information, for example, the merchant profile information may include payment mode, settlement period, settlement account, and the like.

The back end 302 of the acquirer merchant management platform is used for receiving a filing instruction for a target merchant initiated by the front end 301 of the acquirer merchant management platform or receiving a part feeding instruction for the target merchant initiated by the service platform 303, creating a merchant file and storing merchant file information; establishing a sub-account corresponding to the target merchant, and recording to-be-settled data of the target merchant; and calling the intelligent contract platform 304 to create an intelligent contract instance to obtain a merchant order-receiving intelligent contract corresponding to the target merchant; and receiving a query instruction from the acquirer order system 305 to present the data details.

A service platform 303, configured to provide platform services for a target merchant, such as an online mall; calling the back end 302 of the collection-form merchant management platform to perform merchant component feeding; and, when a transaction order payment request is initiated at the service platform for the target merchant, invoking the acquirer order system 305 to initiate a payment application, and the like.

An intelligent contract platform 304 for providing an intelligent contract configuration, generation, and execution environment; receiving an intelligent contract creation request of the acquirer merchant management platform back end 302; an intelligent contract execution request is received from the acquirer clearing system 306.

An acquirer order system 305 for order management, including payment, refund, etc.; receiving a payment application initiated by the service platform 303; invoking the acquirer merchant management platform back end 302 to inquire merchant information; and after the transaction order is paid, sending payment completion information to the acquirer clearing system 306, so that the acquirer clearing system 306 performs clearing settlement processing.

The acquirer clearing and settling system 306 is configured to receive payment completion information sent by the acquirer order system 305, call the intelligent contract platform 304 to execute the merchant acquirer intelligent contract, and complete directional wetting, directional settlement, and the like.

In one example, FIG. 4 is a schematic illustration of an application flow provided herein in response to a merchant profiling instruction for a target merchant. As shown in fig. 4, the application flow specifically includes:

401. and the target merchant initiates a filing instruction on a front-end page at the front end of the collection-form merchant management platform.

Or alternatively

402. The service platform calls the service provided by the back end of the collection and single-form merchant management platform and initiates the package entering instruction.

403. And the back end of the acquirer merchant management platform is used for screening merchant information risks, and after the screening is passed, a merchant file corresponding to the target merchant is established and stored.

404. And checking whether the service platform to which the target merchant belongs has a parent account.

If the service platform to which the target merchant belongs has a parent account, executing 405; if the service platform to which the target merchant belongs does not have a parent account, then 406 is performed.

405. And opening a sub-account for the target merchant under the parent account of the service platform to which the target merchant belongs.

406. And creating a parent account for the service platform to which the target merchant belongs, and opening a child account for the target merchant under the parent account.

407. And calling an intelligent contract platform to generate an intelligent contract template, and writing configuration information such as settlement period, oriented wetting rule, settlement account and the like in merchant archive information into the intelligent contract template to obtain the merchant order-receiving intelligent contract.

In one example, fig. 5 is a schematic structural diagram of an intelligent contract platform provided in the present application. As shown in fig. 5, the smart contract platform includes: an access and exit unit 501, a contract configuration unit 502, a contract management unit 503, an intelligent contract repository 504, a contract operation unit 505, and a contract verification unit 506.

The access receiving unit 501 is configured to dock parties participating in a merchant bill, and perform validity check on data of the parties.

The contract configuration unit 502 is used for being responsible for functions such as intelligent contract template creation, intelligent contract template audit, intelligent contract parameter configuration, intelligent contract template inquiry, intelligent parameter contract submission and the like.

The content of the intelligent contract template can include industry information, contract names, contract descriptions, amounts, start time, end time, and the like. In the merchant profiling link, an intelligent contract instance, namely, a merchant acquiring intelligent contract, is generated according to the intelligent contract template and merchant archive information.

The contract management unit 503 is configured to manage the signed smart contract instance, for example, store and query the smart contract instance, and may store the smart contract instance into a blockchain or a database.

An intelligent contract repository 504 for storing intelligent contract instance environments.

The contract operation unit 505 is used for providing services such as contract signing, contract execution or termination, contract condition registration, contract release, and the like.

At this time, the contract operation unit 505 may include a contract loading module 5051, a business condition triggering module 5052, wherein the contract loading module 5051: and the intelligent contract execution request is responsible for monitoring the outside, and the corresponding intelligent contract instance is pulled from the intelligent contract warehouse according to the intelligent contract execution request, so that the required business data is transmitted.

Service condition triggering module 5052: providing various events triggered by external trusted data, and driving specified intelligent contracts to execute according to the conventions of the intelligent contracts.

And a contract verifying unit 506 for verifying whether the signatures of the parties required for the execution of the smart contract are correct.

In an example, fig. 6 is a schematic flow chart of clearing settlement processing provided in the present application, and as shown in fig. 6, the clearing settlement processing flow specifically includes:

601. and the acquirer clearing and settling system receives the payment completion information.

602. And calling an intelligent contract platform, executing the merchant order-receiving intelligent contract, and performing clear settlement processing. The details are as follows.

603. It is checked if a directional wetting rule exists, if so, 604 is performed, otherwise 605 is performed.

604. And respectively accounting the moisturizing amount to the moisturizing accounts corresponding to the platform service provider and the acquirer, and accounting the residual funds after the moisturizing treatment to the sub-accounts of the target merchant.

605. And (5) accounting the total payment amount to the sub-account of the target merchant.

606. Checking whether the settlement period is satisfied, if so, executing 607, otherwise, directly ending.

607. Checking whether a settlement mode exists, if so, executing 608, otherwise, directly ending.

608. And initiating data settlement processing, executing merchant order-receiving intelligent contracts, and settling the data to be settled of the sub-accounts of the target merchants into the settlement accounts of the target merchants characterized by the settlement mode.

In one example, fig. 7 is a schematic flow chart of querying data to be settled by a target merchant provided in the present application. As shown in fig. 7, the flow includes:

701. and the target merchant initiates a query instruction of the data to be settled on a front-end page of the front end of the acquirer merchant management platform.

Or alternatively

702. And the target merchant initiates a query instruction of the data to be settled on the page of the service platform.

703. And the back end of the acquirer merchant management platform performs admission inspection, determines the sub-account corresponding to the target merchant after the inspection passes, invokes the acquirer clearing and settling system, and initiates a balance inquiry instruction of the sub-account of the target merchant.

704. And the acquirer clearing and settling system inquires the balance of the sub-account of the target merchant according to the balance inquiry instruction and returns the balance.

705. And displaying the balance of the sub-account corresponding to the target merchant on a front-end page at the front end of the acquirer merchant management platform.

Fig. 8 is a schematic structural diagram of a merchant acquiring device based on an intelligent contract. As shown in fig. 8, the apparatus 800 includes:

a response unit 801, configured to obtain merchant profile information corresponding to a target merchant in response to a merchant profiling instruction for the target merchant; the merchant archive information comprises configuration information of a merchant receipt.

The first creating unit 802 is configured to create a merchant profile corresponding to the target merchant based on the merchant profile information, and create a corresponding sub-account for the target merchant under the parent account corresponding to the service platform to which the target merchant belongs; the parent account is used for recording data to be settled corresponding to the service platform; the sub-account is used for recording data to be settled corresponding to the target merchant.

A second creating unit 803 for creating a merchant acquirer smart contract corresponding to the target merchant based on the merchant profile information; the merchant order-receiving intelligent contract is used for carrying out clearing settlement processing on the target merchant.

And the processing unit 804 is configured to invoke the merchant order-receiving intelligent contract after determining that the payment of the transaction order for the target merchant is completed, and perform clearing settlement processing on the transaction order to obtain a merchant settlement result.

Fig. 9 is a schematic structural diagram of another merchant acquiring device based on intelligent contract provided in the present application. As shown in fig. 9, the apparatus 900 includes:

the response unit 901 is configured to obtain merchant profile information corresponding to a target merchant in response to a merchant profiling instruction of the target merchant; the merchant archive information comprises configuration information of a merchant receipt.

The first creating unit 902 is configured to create a merchant profile corresponding to a target merchant based on the merchant profile information, and create a corresponding sub-account for the target merchant under a parent account corresponding to a service platform to which the target merchant belongs; the parent account is used for recording data to be settled corresponding to the service platform; the sub-account is used for recording data to be settled corresponding to the target merchant.

A second creating unit 903, configured to create a merchant acquirer smart contract corresponding to the target merchant based on the merchant profile information; the merchant order-receiving intelligent contract is used for carrying out clearing settlement processing on the target merchant.

And the processing unit 904 is configured to invoke the merchant order-receiving intelligent contract after determining that the payment of the transaction order for the target merchant is completed, and perform clearing and settlement processing on the transaction order to obtain a merchant settlement result.

In one example, the first creating unit 902 is configured to:

determining each primary account included under a parent account corresponding to a service platform to which a target merchant belongs; wherein the primary account characterizes an account that has been created under the parent account;

In one example, the configuration information of the merchant receipt includes template selection information and settlement parameter information, and at this time, the second creating unit 903 is configured to:

Creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the settlement parameter information and the intelligent contract template; wherein the settlement parameter information indicates at least the following information: directional wetting rules, settlement period and settlement mode; the settlement mode represents a settlement account corresponding to the target merchant.

In one example, the clearing settlement processing includes a data clearing processing and a data settlement processing, at which time, the processing unit 904 is configured to:

calling a merchant order-receiving intelligent contract, and based on a directional wetting rule in the merchant order-receiving intelligent contract, performing wetting treatment on the payment amount corresponding to the transaction order to obtain the residual amount after the wetting treatment;

recording the residual amount after the sorting treatment into a sub-account corresponding to a target merchant, and finishing the data sorting treatment of the transaction order to obtain a data sorting result;

and determining a merchant settlement result based on the data sorting result and the data settlement result.

In one example, the apparatus further comprises: the first query unit 905 is configured to determine and display data detail information of the data to be settled in the sub-account corresponding to the target merchant in response to a query instruction of the target merchant for the first target settlement data after recording the remaining amount after the moisturizing process into the sub-account corresponding to the target merchant; the first target settlement data represent to-be-settled data of target merchants.

In one example, the apparatus further comprises: a second query unit 906, configured to determine and display, in response to a query operation of the service platform on the second target settlement data, data detail information of to-be-settled data in a target account matched with the second target settlement data in the service platform; the second target settlement data represents the data to be settled of the service platform, or represents the data to be settled of the merchant under the service platform.

In one example, the apparatus further comprises: an updating unit 907, configured to obtain modified merchant profile information in response to a modification operation on the merchant profile information of the target merchant;

Fig. 10 is a schematic structural diagram of a computer device according to an embodiment of the present application, and as shown in fig. 10, a computer device 1000 includes: memory 1001, processor 1002.

A memory 1001; memory for storing instructions executable by the processor 1002.

Wherein the processor 1002 is configured to perform the method as provided by the above embodiments.

The computer device further comprises a receiver 1003 and a transmitter 1004. The receiver 1003 is configured to receive instructions and data transmitted from an external device, and the transmitter 1004 is configured to transmit instructions and data to the external device.

Embodiments of the present application also provide a computer readable storage medium having stored thereon computer executable instructions that when executed by a processor perform the steps of the smart contract-based merchant order taking method of the method embodiments described above. Wherein the storage medium may be a volatile or nonvolatile computer readable storage medium.

The embodiment of the present application further provides a computer program product, where the computer program product carries computer execution instructions, and the instructions included in the computer execution instructions may be used to execute the steps of the method for acquiring a merchant order based on an intelligent contract in the method embodiment, and specifically, reference may be made to the method embodiment, which is not described herein.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all alternative embodiments, and that the acts and modules referred to are not necessarily required in the present application.

It should be further noted that, although the steps in the flowchart are sequentially shown as indicated by arrows, the steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in the flowcharts may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order in which the sub-steps or stages are performed is not necessarily sequential, and may be performed in turn or alternately with at least a portion of the sub-steps or stages of other steps or other steps.

It should be understood that the above-described device embodiments are merely illustrative, and that the device of the present application may be implemented in other ways. For example, the division of the units/modules in the above embodiments is merely a logic function division, and there may be another division manner in actual implementation. For example, multiple units, modules, or components may be combined, or may be integrated into another system, or some features may be omitted or not performed.

In addition, each functional unit/module in each embodiment of the present application may be integrated into one unit/module, or each unit/module may exist alone physically, or two or more units/modules may be integrated together, unless otherwise specified. The integrated units/modules described above may be implemented either in hardware or in software program modules.

The integrated units/modules, if implemented in hardware, may be digital circuits, analog circuits, etc. Physical implementations of hardware structures include, but are not limited to, transistors, memristors, and the like. The processor may be any suitable hardware processor, such as CPU, GPU, FPGA, DSP and ASIC, etc., unless otherwise specified. Unless otherwise indicated, the storage elements may be any suitable magnetic or magneto-optical storage medium, such as resistive Random Access Memory RRAM (Resistive Random Access Memory), dynamic Random Access Memory DRAM (Dynamic Random Access Memory), static Random Access Memory SRAM (Static Random-Access Memory), enhanced dynamic Random Access Memory EDRAM (Enhanced Dynamic Random Access Memory), high-Bandwidth Memory HBM (High-Bandwidth Memory), hybrid Memory cube HMC (Hybrid Memory Cube), etc.

The integrated units/modules may be stored in a computer readable memory if implemented in the form of software program modules and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a memory, including several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned memory includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments. The technical features of the foregoing embodiments may be arbitrarily combined, and for brevity, all of the possible combinations of the technical features of the foregoing embodiments are not described, however, all of the combinations of the technical features should be considered as being within the scope of the disclosure.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A merchant order receiving method based on intelligent contracts, the method comprising:

2. The method of claim 1, wherein creating a corresponding sub-account for the target merchant under a parent account corresponding to a service platform to which the target merchant belongs comprises:

3. The method of claim 1, wherein the configuration information of the merchant acquirer includes template selection information and settlement parameter information; the creating a merchant order-receiving intelligent contract corresponding to the target merchant based on the merchant profile information comprises the following steps:

4. A method according to claim 3, wherein the clearing settlement processing includes a data clearing processing and a data settlement processing; the step of calling the merchant order-receiving intelligent contract, and performing clear settlement processing on the transaction order to obtain a merchant settlement result, which comprises the following steps:

5. The method of claim 4, wherein after recording the remaining amount after the moisturizing process into the sub-account corresponding to the target merchant, the method further comprises:

6. The method according to claim 1, wherein the method further comprises:

7. The method according to any one of claims 1-6, further comprising:

8. A merchant order receiving device based on intelligent contracts, comprising:

9. A computer device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the smart contract-based merchant order taking method of any one of claims 1 to 7.

10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for implementing a smart contract based merchant order taking method as claimed in any one of claims 1 to 7.