CN111626848A - Data processing method and system - Google Patents
Data processing method and system Download PDFInfo
- Publication number
- CN111626848A CN111626848A CN202010500329.XA CN202010500329A CN111626848A CN 111626848 A CN111626848 A CN 111626848A CN 202010500329 A CN202010500329 A CN 202010500329A CN 111626848 A CN111626848 A CN 111626848A
- Authority
- CN
- China
- Prior art keywords
- account
- target node
- limit
- service request
- setting
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Abstract
The embodiment of the application discloses a data processing method and a data processing system, which are applied to an alliance chain, wherein the alliance chain comprises a target node and other nodes; the method comprises the following steps: a target node receives a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node; the target node broadcasts the service request in the alliance chain so that the non-target node receives the service request; and setting the limit to be set for setting the limit corresponding to the account. After the technical scheme of the application is adopted, when a user needs to adjust the transaction limit of each account, the user can set the limit of each account through any node of the alliance chain.
Description
Technical Field
The present application relates to the field of block chain technology, and in particular, to a data processing method and system.
Background
The property security of the user is closely related to the account transacted by the user at the financial institution, and the factor affecting the security level of the account may be the transaction limit of the account.
The transaction limit of the account can limit the maximum amount of each transaction of the user, and if the account of the user is stolen, the property loss of the user can be effectively reduced.
Currently, each financial institution sets a default transaction limit for the user's account, with different financial institutions setting different default transaction limits.
When the user has a plurality of accounts of different financial institutions, each financial institution can only manage the corresponding account, and if the transaction limit of each account needs to be adjusted, the user needs to go to the financial institution corresponding to each account to adjust the transaction limit respectively, so that the transaction limit cannot be adjusted uniformly.
Disclosure of Invention
In order to solve the technical problem, the application provides a data processing method and system, which can set the transaction limit of each account in only one financial institution.
The embodiment of the application discloses the following technical scheme:
in a first aspect, an embodiment of the present application provides a data processing method, which is applied to a federation chain, where the federation chain includes a target node and a non-target node; the method comprises the following steps: the target node receives a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node; the target node broadcasts the service request in the alliance chain so that the non-target node receives the service request; and the limit to be set is used for setting the limit corresponding to the account.
As a possible implementation, when the account is an account corresponding to the target node, the method further includes:
and the target node sets the limit corresponding to the account according to the limit to be set.
As a possible implementation manner, the service request further includes an identity; before setting the limit corresponding to the account, the method further comprises the following steps:
when the account is the account corresponding to the target node, the target node judges whether the identity mark corresponds to the account or not;
and when the account is the account corresponding to the non-target node, the non-target node judges whether the identity mark corresponds to the account.
As a possible implementation, before the target node broadcasts the service request in the federation chain, the method further includes:
the target node determining the number of times a limit on the account is set;
and when the times are greater than a preset value, the target node discards the service request.
As a possible implementation, the method further comprises:
when the account is the account corresponding to the target node, the target node judges whether the limit to be set exceeds the maximum limit; if so, the target node generates first setting failure information;
when the account is the account corresponding to the non-target node, the non-target node judges whether the limit to be set exceeds the maximum limit; and if so, the non-target node generates second setting failure information.
In a second aspect, an embodiment of the present application provides a data processing system, including: a target node and a non-target node; the target node and the non-target node are both nodes in a federation chain; the target node is used for receiving a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node; the non-target node is configured to receive the service request after the target node broadcasts the service request in the federation chain; and the limit to be set is used for setting the limit corresponding to the account.
As a possible implementation manner, when the account is an account corresponding to the target node, the target node is further configured to set a limit corresponding to the account according to the limit to be set.
As a possible implementation manner, the service request further includes an identity; when the account is the account corresponding to the target node, the target node is further configured to determine whether the identity corresponds to the account;
and when the account is the account corresponding to the non-target node, the non-target node is further used for judging whether the identity mark corresponds to the account.
As a possible implementation, the target node is further configured to determine a number of times a limit on the account is set; and when the times are greater than a preset value, discarding the service request.
As a possible implementation manner, when the account is an account corresponding to the target node, the target node is further configured to determine whether the limit to be set exceeds a maximum limit; if so, the target node generates first setting failure information; when the account is the account corresponding to the non-target node, the non-target node is further used for judging whether the limit to be set exceeds the maximum limit; and if so, the non-target node generates second setting failure information.
According to the technical scheme, the embodiment of the application has the following advantages:
a data processing method and system are applied to a alliance chain, wherein the alliance chain comprises a target node and other nodes; the method comprises the following steps: the target node receives a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node; the target node broadcasts the service request in the alliance chain so that the non-target node receives the service request; and the limit to be set is used for setting the limit corresponding to the account. After the technical scheme of the application is adopted, when a user needs to adjust the transaction limit of each account, the user sends the account identifier needing to be adjusted and any node on a to-be-set transaction limit sending block chain, such as a target node, and then the target node broadcasts the account identifier needing to be adjusted and the to-be-set transaction limit on the alliance chain, so that other nodes receive the account identifiers corresponding to other financial institutions and the to-be-set transaction limit, and therefore the user can set the limit of each account through any node of the alliance chain.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of a data processing method according to an embodiment of the present application;
fig. 2 is a schematic diagram of a data processing system according to an embodiment of the present application.
Detailed Description
At present, a user owns accounts of a plurality of different financial institutions (such as banks), and when the user needs to uniformly modify the transaction limit of the account, the user needs to transact related services respectively to a bank website without home. For example, when the user owns the account a1 of bank a and the account B1 of bank B, and the user wants to set the transaction limit of account a1 and the transaction limit of account B1 to the value C, the user needs to set the transaction limit of account a1 to the value C separately from bank a and also needs to set the transaction limit of account B1 to the value C separately from bank B, which is very inconvenient for the user.
In order to solve the problem of setting the transaction limit of the account, the application provides a data processing method which is applied to a alliance chain, and each node in the alliance chain corresponds to different banks. When the user needs to set the transaction limit of each account, the user only needs to go to any bank to handle related services.
Specifically, the bank a receives a service request submitted by the user, where the service request includes an account (for example, an ID of the account) that the user needs to modify and a limit to be set, and it should be noted that, when the service request includes a plurality of accounts and a plurality of limits to be set, the accounts and the limits to be set are in one-to-one correspondence.
After receiving the service request submitted by the user, the bank a broadcasts the service request on the federation chain so that other nodes (e.g., the bank B) on the federation chain receive the service request.
After the bank B receives the service request, the bank B may set the transaction limit of the account according to the account and the limit to be set carried in the service request. Therefore, the user does not need to transact related services at each bank outlet, and the user transacts related services at any bank outlet, so that the transaction limit of the account can be uniformly set.
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The first embodiment is as follows:
the first embodiment of the present application provides a data processing method, and the following describes an embodiment of the present application with reference to the accompanying drawings.
Referring to fig. 1, the figure is a flowchart of a data processing method provided in an embodiment of the present application.
The data processing method is applied to a alliance chain, wherein the alliance chain comprises a target node and a non-target node; the method comprises the following steps:
step 101: the target node receives a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node.
It should be noted that the federation chain may be composed of multiple banks, and each bank corresponds to one node. The target node may be a node that receives a service request submitted by a user, the target node may be any bank, and the user may be a customer corresponding to the bank or not. That is, the bank corresponding to any node in the federation chain for the user can submit the service request.
The service request carries an account and a limit to be set, and when the service request comprises a plurality of accounts and a plurality of limits to be set, the accounts and the transaction limit to be set are in one-to-one correspondence. The service request including three accounts and three limits to be set is taken as an example for detailed description.
The three accounts include: account a, account B, and account C; the three limits to be set include: quota A-1, quota B-1, and quota C-1.
The one-to-one correspondence relationship between the account and the transaction limit to be set is specifically as follows: account A corresponds to limit A-1; account B corresponds to limit B-1; account C corresponds to limit C-1.
As a possible implementation, when the account is an account corresponding to the target node, the method further includes: and the target node sets the limit corresponding to the account according to the limit to be set.
It can be understood that, in some scenarios, the user is just a customer of the bank corresponding to the target node, and the account a that the user needs to set and the limit a-1 to be set also just correspond to the bank. At this time, after receiving the service request submitted by the user, the bank may set the transaction limit of the account a of the user to a-1 directly according to the service request. After the setting, the target node broadcasts the service request in the alliance chain.
In combination with the above scenario, the target node may also set the transaction limit of account a to a-1 after broadcasting the service request in the federation chain.
In other scenarios, in order to improve the security of the account, the service request also needs to carry the identity of the user.
Before setting the transaction limit of the account A, the target node needs to verify the identity of the user to ensure that the account A set by the user is the user and not the account of other people.
In still other scenarios, to improve the security of the account, the target node may also obtain in advance the number of times that account a has recently modified the transaction limit before setting the transaction limit for account a, for example: the number of times the transaction limit for account a was modified within 30 days. The amount of the additive is not limited to 30 days, but may be 15 days, 7 days or 1 day, and the time can be selected by those skilled in the art according to actual conditions.
When the number of times that the transaction limit of the account A is modified in the near future exceeds a preset value, the target node discards the service request, that is, the user is refused to modify the transaction limit of the account A.
Specifically, when the transaction limit of the account is set more than 3 times within 1 day, the target node discards the service request. The number of times of the default value is not specifically limited to be 3 times, but can also be 5 times or more, and a person skilled in the art can select the number of times according to actual conditions.
In other scenarios, in order to improve the security of the account, before setting the transaction limit of the account a, the target node further needs to determine whether the limit a-1 to be set, which is carried in the service request and corresponds to the account a, exceeds the maximum limit; the maximum limit can be the highest limit of the account A consumed in a single day specified by the bank, namely, after the maximum limit is exceeded, the account A can not pay any more.
That is, to ensure the security of the account, the user may set the transaction limit for account a within a maximum limit.
Step 102: the target node broadcasts the service request in the alliance chain so that the non-target node receives the service request; and the limit to be set is used for setting the limit corresponding to the account.
It should be noted that the non-target node is a node other than the target node in the federation chain.
After the non-target node receives the service request, the transaction limit of the account B can be set according to the account B carried in the service request and the limit B-1 to be set. The process of setting the transaction limit of the account B by the non-target node is similar to the process of setting the transaction limit of the account a by the target node, which may specifically refer to step 101, and is not described herein again.
After the non-target node receives the service request, the non-target node may set a transaction limit of the account according to the account and the limit to be set carried in the service request. Therefore, the user does not need to transact related services at each bank outlet, and the user transacts related services at any bank outlet, so that the transaction limit of the account can be uniformly set.
The embodiment of the application provides a data processing method, which is applied to a alliance chain, wherein the alliance chain comprises a target node and other nodes; the method comprises the following steps: the target node receives a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node; the target node broadcasts the service request in the alliance chain so that the non-target node receives the service request; and the limit to be set is used for setting the limit corresponding to the account. After the technical scheme of the application is adopted, when a user needs to adjust the transaction limit of each account, the user sends the account identifier needing to be adjusted and any node on a to-be-set transaction limit sending block chain, such as a target node, and then the target node broadcasts the account identifier needing to be adjusted and the to-be-set transaction limit on the alliance chain, so that other nodes receive the account identifiers corresponding to other financial institutions and the to-be-set transaction limit, and therefore the user can set the limit of each account through any node of the alliance chain.
Example two:
the second embodiment of the present application provides a data processing system, and the following describes an embodiment of the present application with reference to the drawings.
Referring to fig. 2, a schematic diagram of a data processing system according to an embodiment of the present application is shown.
An embodiment of the present application provides a data processing system, including: a target node 201 and a non-target node 202.
The target node 201 and the non-target node 202 are both nodes in a federation chain.
The target node 201 is configured to receive a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node.
The non-target node 202 is configured to receive the service request after the target node 201 broadcasts the service request in the federation chain; and the limit to be set is used for setting the limit corresponding to the account.
As a possible implementation manner, when the account is an account corresponding to the target node 201, the target node 201 is further configured to set a limit corresponding to the account according to the limit to be set.
As a possible implementation manner, the service request further includes an identity; when the account is an account corresponding to the target node 201, the target node 201 is further configured to determine whether the identity corresponds to the account.
When the account is an account corresponding to the non-target node 202, the non-target node 202 is further configured to determine whether the identity corresponds to the account.
As a possible implementation, the target node 201 is further configured to determine the number of times the quota on the account is set; and when the times are greater than a preset value, discarding the service request.
As a possible implementation manner, when the account is an account corresponding to the target node 201, the target node 201 is further configured to determine whether the limit to be set exceeds a maximum limit; if yes, the target node 201 generates first setting failure information.
When the account is an account corresponding to the non-target node 202, the non-target node 202 is further configured to determine whether the limit to be set exceeds a maximum limit; if so, the non-target node 202 generates second setting failure information.
An embodiment of the present application provides a data processing system, including: a target node and a non-target node; the target node and the non-target node are both nodes in a federation chain; the target node is used for receiving a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node; the non-target node is configured to receive the service request after the target node broadcasts the service request in the federation chain; and the limit to be set is used for setting the limit corresponding to the account. After the technical scheme of the application is adopted, when a user needs to adjust the transaction limit of each account, the user sends the account identifier needing to be adjusted and any node on a to-be-set transaction limit sending block chain, such as a target node, and then the target node broadcasts the account identifier needing to be adjusted and the to-be-set transaction limit on the alliance chain, so that other nodes receive the account identifiers corresponding to other financial institutions and the to-be-set transaction limit, and therefore the user can set the limit of each account through any node of the alliance chain.
Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium may be at least one of the following media: various media that can store program codes, such as read-only memory (ROM), RAM, magnetic disk, or optical disk.
It should be noted that, in the present specification, all the embodiments are described in a progressive manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus and system embodiments, since they are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described embodiments of the apparatus and system are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only one specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A data processing method is applied to a alliance chain, wherein the alliance chain comprises a target node and a non-target node; the method comprises the following steps:
the target node receives a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node;
the target node broadcasts the service request in the alliance chain so that the non-target node receives the service request;
and the limit to be set is used for setting the limit corresponding to the account.
2. The method according to claim 1, wherein when the account is an account corresponding to the target node, the method further comprises:
and the target node sets the limit corresponding to the account according to the limit to be set.
3. The method of claim 1, wherein the service request further comprises an identity; before setting the limit corresponding to the account, the method further comprises the following steps:
when the account is the account corresponding to the target node, the target node judges whether the identity mark corresponds to the account or not;
and when the account is the account corresponding to the non-target node, the non-target node judges whether the identity mark corresponds to the account.
4. The method of claim 1, wherein before the target node broadcasts the service request in the federation chain, the method further comprises:
the target node determining the number of times a limit on the account is set;
and when the times are greater than a preset value, the target node discards the service request.
5. The method according to any one of claims 1-4, further comprising:
when the account is the account corresponding to the target node, the target node judges whether the limit to be set exceeds the maximum limit; if so, the target node generates first setting failure information;
when the account is the account corresponding to the non-target node, the non-target node judges whether the limit to be set exceeds the maximum limit; and if so, the non-target node generates second setting failure information.
6. A data processing system, comprising: a target node and a non-target node; the target node and the non-target node are both nodes in a federation chain;
the target node is used for receiving a service request; the service request comprises an account and a limit to be set, and the account corresponds to the limit to be set; the account is an account corresponding to the target node or an account corresponding to the non-target node;
the non-target node is configured to receive the service request after the target node broadcasts the service request in the federation chain; and the limit to be set is used for setting the limit corresponding to the account.
7. The system according to claim 6, wherein when the account is an account corresponding to the target node, the target node is further configured to set a quota corresponding to the account according to the quota to be set.
8. The system of claim 6, wherein the service request further comprises an identity; when the account is the account corresponding to the target node, the target node is further configured to determine whether the identity corresponds to the account;
and when the account is the account corresponding to the non-target node, the non-target node is further used for judging whether the identity mark corresponds to the account.
9. The system of claim 6, wherein the target node is further configured to determine a number of times a limit on the account is set; and when the times are greater than a preset value, discarding the service request.
10. The system according to any one of claims 6 to 9, wherein when the account is an account corresponding to the target node, the target node is further configured to determine whether the limit to be set exceeds a maximum limit; if so, the target node generates first setting failure information;
when the account is the account corresponding to the non-target node, the non-target node is further used for judging whether the limit to be set exceeds the maximum limit; and if so, the non-target node generates second setting failure information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010500329.XA CN111626848A (en) | 2020-06-04 | 2020-06-04 | Data processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010500329.XA CN111626848A (en) | 2020-06-04 | 2020-06-04 | Data processing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111626848A true CN111626848A (en) | 2020-09-04 |
Family
ID=72272630
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010500329.XA Pending CN111626848A (en) | 2020-06-04 | 2020-06-04 | Data processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111626848A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112069526A (en) * | 2020-10-15 | 2020-12-11 | 深圳壹账通智能科技有限公司 | Block chain-based account attribute processing method and device and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107332701A (en) * | 2017-06-26 | 2017-11-07 | 中国人民银行数字货币研究所 | The method and system of management node |
| CN108683539A (en) * | 2018-05-21 | 2018-10-19 | 腾讯科技（深圳）有限公司 | Management method, device, medium and the electronic equipment of block chain network |
| CN109002729A (en) * | 2018-07-09 | 2018-12-14 | 福建省农村信用社联合社 | A kind of customer privacy data managing method based on financial block chain |
| CN109063169A (en) * | 2018-08-17 | 2018-12-21 | 福建省农村信用社联合社 | A kind of customer data management system based on block chain |
| CN109409865A (en) * | 2018-09-18 | 2019-03-01 | 平安科技（深圳）有限公司 | Pay limit synchronization adjustment method, device, computer equipment and storage medium |
| CN110868424A (en) * | 2019-11-26 | 2020-03-06 | 深圳市信联征信有限公司 | Data sharing method and device based on block chain, computer equipment and storage medium |
| US20200082388A1 (en) * | 2018-09-06 | 2020-03-12 | STAR BIT Innovation Co., Ltd. | Authenticating server and method for transactions on blockchain |
| CN111179067A (en) * | 2019-12-31 | 2020-05-19 | 杭州趣链科技有限公司 | Block chain-based customer information exchange system between banks |
-
2020
- 2020-06-04 CN CN202010500329.XA patent/CN111626848A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107332701A (en) * | 2017-06-26 | 2017-11-07 | 中国人民银行数字货币研究所 | The method and system of management node |
| CN108683539A (en) * | 2018-05-21 | 2018-10-19 | 腾讯科技（深圳）有限公司 | Management method, device, medium and the electronic equipment of block chain network |
| CN109002729A (en) * | 2018-07-09 | 2018-12-14 | 福建省农村信用社联合社 | A kind of customer privacy data managing method based on financial block chain |
| CN109063169A (en) * | 2018-08-17 | 2018-12-21 | 福建省农村信用社联合社 | A kind of customer data management system based on block chain |
| US20200082388A1 (en) * | 2018-09-06 | 2020-03-12 | STAR BIT Innovation Co., Ltd. | Authenticating server and method for transactions on blockchain |
| CN109409865A (en) * | 2018-09-18 | 2019-03-01 | 平安科技（深圳）有限公司 | Pay limit synchronization adjustment method, device, computer equipment and storage medium |
| CN110868424A (en) * | 2019-11-26 | 2020-03-06 | 深圳市信联征信有限公司 | Data sharing method and device based on block chain, computer equipment and storage medium |
| CN111179067A (en) * | 2019-12-31 | 2020-05-19 | 杭州趣链科技有限公司 | Block chain-based customer information exchange system between banks |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112069526A (en) * | 2020-10-15 | 2020-12-11 | 深圳壹账通智能科技有限公司 | Block chain-based account attribute processing method and device and storage medium |
| WO2022078396A1 (en) * | 2020-10-15 | 2022-04-21 | 深圳壹账通智能科技有限公司 | Account attribute processing method based on blockchain, and device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107846278B (en) | Intelligent contract processing method and device | |
| CN108154367B (en) | Block chain service checking method and device | |
| KR101827373B1 (en) | Block window module having agreement algorithm for limiting mining, managing server and virtual money exchange system and method | |
| CN110232565B (en) | Resource clearing method, device, computer equipment and storage medium | |
| CN104966229A (en) | Information processing method and credit platform | |
| CN113837732A (en) | Internet resource transfer method, account transfer method and device | |
| US8725605B1 (en) | Method and system for managing service accounts | |
| CN111614709B (en) | Partition transaction method and system based on block chain | |
| CN111861477A (en) | Block chain-based post-transaction data processing method and device and computer equipment | |
| US20180137476A1 (en) | Intelligent authentication process | |
| CN107527222B (en) | Information processing method, device and system | |
| CN108009818B (en) | Online payment method and system based on distributed network | |
| CN101964093B (en) | Invoice Number method of payment, payment platform and payment system | |
| CN108537520B (en) | Method and device for accessing third-party payment transaction | |
| CN111260371A (en) | Recommendation method and device for domestic service route, storage medium and electronic equipment | |
| CN108492109B (en) | Electronic device, dynamic code request processing method and storage medium | |
| CN115456769A (en) | Financing credit transmission method based on block chain system and block chain system | |
| CN111626848A (en) | Data processing method and system | |
| CN111667271A (en) | Digital currency using method and device based on region and time and electronic equipment | |
| CN112884562B (en) | Mortgage processing method and device based on blockchain and readable storage medium | |
| CN110728580A (en) | Financial transaction control method | |
| CN111177262A (en) | Block chain consensus method, related device and system | |
| KR102107454B1 (en) | System for multiplication of financial payment networks, method for financial services using the same and computer program for the same | |
| US20230298038A1 (en) | A computer implemented method and system for requesting consent from a consumer to complete an action | |
| CN113781230A (en) | Transaction processing method and device based on block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |