CN114372788A - Third party payment cloud account member system - Google Patents
Third party payment cloud account member system Download PDFInfo
- Publication number
- CN114372788A CN114372788A CN202111402417.7A CN202111402417A CN114372788A CN 114372788 A CN114372788 A CN 114372788A CN 202111402417 A CN202111402417 A CN 202111402417A CN 114372788 A CN114372788 A CN 114372788A
- Authority
- CN
- China
- Prior art keywords
- information
- module
- client
- customer
- service
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/085—Payment architectures involving remote charge determination or related payment systems
- G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses a third-party payment cloud account member system which sequentially comprises a customer service product layer, a customer service information supporting layer and an information centralized processing layer from top to bottom; the customer service product layer corresponds to a customer service platform, provides a uniform login center, a personal/enterprise customer center, a protocol center and an authentication registration center aiming at a customer network access mode according to the service characteristics paid by a third party, and performs uniform maintenance by a uniform standard network access mode and a network access protocol; the customer service information supporting layer corresponds to a customer information platform, classifies and normalizes customer information acquired by the customer service platform, and modularly stores information with different attributes; the information centralized processing layer corresponds to a client centralized processing platform and carries out unified modular management on information of different clients. The method and the system solve the problem of member service with complex diversity under the background of different requirements of commercial customers in various industries, and realize unified authentication and maintenance management among all service subsystems.
Description
Technical Field
The invention relates to the technical field of third-party transactions, in particular to a third-party payment cloud account member system.
Background
The third party payment industry standard member system mainly takes management and maintenance of information flow water as main parts, develops basic payment products depending on payment requirements of customers, and pays more attention to basic payment capabilities such as performance, channels, price and amount.
At present, a standardized membership system is not available in the industry, payment basic products are developed mainly depending on the payment requirements of customers, unified management of customer information is lacked, standard modular membership services cannot be provided aiming at business customer systematic construction, an industrialized solution, financial and financing requirements, higher-level compliance, cost reduction and efficiency improvement and other services, and accordingly membership information is disorderly and difficult to maintain. Generally, a client accesses to a third party payment member system, accesses to a payment system through a product layer, and completes a final payment service using a payment service provided by the payment system. There is no unified standard for accessing network and unified maintenance of membership information among various service subsystems (such as financing, purse, insurance, fund and fund consumption) output by the membership system, when there is a service difference in the membership system, it is necessary to store and manage respective membership data among the service subsystems, if there is no global membership attribute between the service processing subsystems, manual integration is performed when there is a difference, and the workload is huge. Even when the service is normal, the existing member system lacks a uniform service subsystem processing link, and the service monitoring and early warning are also dispersed in each service subsystem, which is not beneficial to global control.
Therefore, the third party payment member system in the prior art still needs to be improved.
Disclosure of Invention
The invention aims to provide a third party payment cloud account member system to solve the problems in the technical background.
In order to achieve the purpose, the invention adopts the following technical scheme:
a third party payment cloud account member system is of a three-layer structure and sequentially comprises a customer service product layer, a customer service information supporting layer and an information centralized processing layer from top to bottom, wherein a lower layer between adjacent layers provides service for an upper layer; wherein the content of the first and second substances,
the customer service product layer is used for providing a uniform entrance, corresponds to a customer service platform, and provides a uniform login center, a personal/enterprise customer center, a protocol center and an authentication registration center according to the service characteristics of third party payment and aiming at the network access mode (such as mobile phone, official network, API and the like) of a customer, so as to perform uniform maintenance in a uniform standard network access mode and a network access protocol;
the customer service information supporting layer provides uniform member image service for each business subsystem (such as financing, wallet, insurance, fund and fund payment), and corresponds to a customer information platform which classifies and normalizes customer information acquired by the customer service platform, modularly stores information with different attributes, and stores basic information, protocol information, authority information and ciphertext information as required;
the information centralized processing layer corresponds to a client centralized processing platform, and the client centralized processing platform is used for uniformly and modularly managing the information of different clients stored by the client information platform.
Preferably, the third party payment services originate from different service subsystems, including, but not limited to, any one or more of financing, purse, insurance, fund, and fund consumption.
Preferably, the customer service platform includes, but is not limited to, one or more of a login center module, a registration authentication center module, a personal customer center module, an enterprise customer center module, a customer subscription center module, and an open service interface module.
More preferably, the login center module is configured to implement functions including at least one of: ordinary login, trusted login, SSO login, API login, quick login and logout;
the registered authentication center module is configured to realize functions including at least one of the following: registration, information additional recording, activation, personal authentication, enterprise authentication and import authentication;
the personal customer hub module or the enterprise customer hub module configured to perform functions including at least one of: password service, information maintenance, operator management, account logout, security service, operator authority, mobile phone service and login name management;
the client subscription center module is configured to implement functions including at least one of: agreement signing, agreement contract clearing, agreement inquiry and agreement renewal.
Preferably, the customer information platform includes, but is not limited to, one or more of a customer identification module, a customer information module, a unified view module, a product account management module, a subscription information module, a quota management module, a rights management module, and an information desensitization module.
More preferably, the client information module is configured to store information including one or more of basic information, offline information, authentication information, classification information, asset information, role information, address information, and operation logs;
the authority management module or the quota management module is configured to store information including one or more of client authority, operator authority, account information, product accounts, transaction accumulation, client quota, account quota, and journal;
the signing information module is configured to store information including one or more of signing examples, process configuration, signing main bodies, operation logs, sales plan information and order information;
the information desensitization module is configured to realize one or more functions of desensitization inquiry and desensitization audit.
Preferably, the client centralized processing platform includes, but is not limited to, one or more of a unified authentication module, a unified archive module, a unified ID module and an information mapping module; wherein the content of the first and second substances,
the uniform authentication module is used for performing uniform authentication and identification on the authenticity of client information for the client accessing the network;
the uniform file module is used for uniformly establishing an account opening protocol file for the client accessing the network aiming at the payment service of each third party and establishing the basic information and the account information of the client when the file is activated;
the uniform ID module is used for uniformly configuring an ID for the client accessing the network;
and the information mapping module is used for mapping the client information to different client accounts through the client role model.
More preferably, the client role model includes: customer attributes, customer account attributes, operator (role) attributes, account attributes; wherein the content of the first and second substances,
the client attribute is configured to complete authentication and verification after a client applies for network access, so that basic service is provided for the client, and when network access is applied for multiple times and functions of different business subsystems (financing, wallet, insurance, fund consumption and the like) are completed, the client does not need multiple authentication and application and authentication and verification;
the client account attribute is configured to provide different service capabilities for the client and generate different client accounts when the client completes product function applications under different service subsystems (financing, wallet, insurance, fund consumption and the like);
the operator (role) attribute is configured to assign different management authorities to the client after the client accesses the network;
the account attributes are configured to be combined and configured according to different requirements of customers, and personalized requirements are met.
Preferably, the system further comprises a primary/secondary data platform, wherein the primary/secondary data platform comprises a metadata module, a primary data configuration module and a secondary data configuration module.
Preferably, the system further comprises a general technical platform, wherein the general technical platform comprises a general integration module, a general query module, a near-end access module and a data consistency module.
Compared with the prior art, the technical scheme of the invention has the following beneficial effects:
the application provides a third party payment cloud account member system for solve the member service problem that there is complicated variety under the different demand backgrounds of numerous trade companies, this application can carry out the configuration of combination according to the different demands of customer, also can export alone, reduces implementation cost, and the entry to the different business of upper strata simultaneously realizes the unified management of customer data. The method and the system are convenient for the serial connection of the customer information under the subsystems of various services in the payment system, are beneficial to the transparentization and unification of the customer management processing flow, and realize the unified authentication and maintenance management among the service subsystems.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate embodiments of the application and, together with the description, serve to explain the application and are not intended to limit the application. In the drawings:
FIG. 1 is a diagram of the overall system architecture of the system in an embodiment of the invention;
FIG. 2 is a diagram illustrating functional modules included in the system according to an embodiment of the present invention;
FIG. 3 is a block diagram of processing functions included in the customer service platform of the system in an embodiment of the invention;
FIG. 4 is a block diagram of processing functions included in the client information platform of the system in an embodiment of the invention;
FIG. 5 is a flow chart of client registration included in an embodiment of the present invention;
FIG. 6 is a block diagram of a client authentication function included in an embodiment of the present invention;
FIG. 7 is a flow diagram of a verification process for authentication of a client as embodied in an embodiment of the present invention;
fig. 8 is a flow chart of a client contract application included in an embodiment of the present invention;
FIG. 9 is a functional block diagram of a client role model included in an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and effects of the present invention clearer and clearer, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order, it being understood that the data so used may be interchanged under appropriate circumstances. Furthermore, the terms "comprises," "comprising," and any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Fig. 1 is a general architecture diagram of a system in an embodiment of the present application.
As shown in fig. 1, the third party payment cloud account member system of the present application includes three data services, the top layer is a customer service product layer, and mainly provides a unified inlet of the cloud account member system, including various main sub-modules for different information processing. The middle layer is a customer service information support layer and provides uniform member portrait service for all business subsystems (such as financing, wallet, insurance, fund and fund consumption). The lowest layer is an information centralized processing layer, and member information generated by each service subsystem (such as financing, wallet, insurance, fund and fund consumption) is subjected to unified modular management.
Fig. 2 is a functional block diagram included in the system in the embodiment of the present application.
As shown in fig. 2, the third party payment cloud account membership system may be divided into: the system comprises a customer service platform, a customer information platform, a main/auxiliary data platform, a customer centralized processing platform and a general technical platform.
Specifically, the customer service platform comprises a login center module, a registration authentication center module, a personal customer center module, an enterprise customer center module, a customer signing center module and an open service interface module.
The client information platform comprises a client identification module, a client information module, a unified view module, a product account management module, a signing information module, a quota management module, a permission management module and an information desensitization module.
The main/auxiliary data platform comprises a metadata module, a main data configuration module and an auxiliary data configuration module.
The client centralized processing platform comprises a uniform authentication module, a uniform archive module, a uniform ID module and an information mapping module.
The universal technology platform comprises a universal integration module, a universal query module, a near-end access module and a data consistency module.
FIG. 3 is a block diagram of processing functions included in the customer service platform of the system in an embodiment of the invention.
As shown in fig. 3, the customer service platform: according to the service characteristics of third party payment, aiming at the client network access mode (such as a mobile phone, an official network, an API and the like), a unified login center, a personal/enterprise client center, a protocol center and an authentication registration center are provided, and unified maintenance is carried out by a unified standard network access mode and a network access protocol.
Different business protocols are generated through different business subsystems (such as financing, wallet, insurance, fund elimination and the like), protocol signing and management maintenance are carried out, a unified login center is provided, and system disorder and risk invasion caused by different data and entries of different businesses are prevented through unified external login service and information acquisition, so that management disorder is avoided, and manual integration is reduced.
Fig. 4 is a block diagram of processing functions included in the client information platform of the system according to the embodiment of the present invention.
As shown in fig. 4, the customer information platform: the method comprises the steps of classifying and regulating customer information collected by a customer service platform, performing modular storage on information with different attributes, storing basic information, protocol information, authority information and ciphertext information as required, and acquiring different account information such as wallets, financing, credit credits and the like according to self requirements by using different business subsystems (such as financing, wallets, insurance, fund consumption and the like) on the upper layer.
Meanwhile, according to the customer portrait, the enterprise customer can be provided with an industrial solution and an additional service under the condition of meeting supervision, and the value-added service of the customer is improved on the premise of reducing the cost.
Specifically, the login center module is configured to implement the functions of: ordinary login, trusted login, SSO login, API login, quick login and logout.
A registry certificate authority module configured to perform functions comprising: registration, information additional recording, activation, personal authentication, enterprise authentication and import authentication;
a personal/business customer center module configured to perform functions including: password service, information maintenance, operator management, account logout, security service, operator authority, mobile phone service and login name management;
a customer subscription center module configured to implement functions comprising: agreement signing, agreement contract clearing, agreement inquiry and agreement renewal.
Fig. 5 is a flow chart of client registration included in an embodiment of the present invention.
As shown in fig. 5, a client completes an access application through a client access mode (e.g., a mobile phone, an official network, an API, etc.) through processes of applying, signing, activating, etc., and establishes an account agreement file for each business subsystem (e.g., financing, wallet, insurance, fund withdrawal, etc.) during access, and establishes basic information and account information of the client during activation.
Specifically, the client information module is configured to store information including basic information, offline information, authentication information, classification information, asset information, role information, address information, and an operation log.
The system comprises a permission management module or a quota management module, wherein the information stored by the permission management module or the quota management module comprises client permission, operator permission, account information, product accounts, transaction accumulation, client quota, account quota and journal.
And the signing information module is configured to store information including signing examples, process configuration, signing main bodies, operation logs, sales plan information and order information.
And the information desensitization module is configured to realize functions including desensitization inquiry and desensitization audit.
Fig. 6 is a block diagram of a client authentication function included in the embodiment of the present invention.
As shown in fig. 6, when a client accesses the network, the cloud account member system needs to perform authentication and identification of authenticity of client information, including elements such as identity information, bank information, and enterprise information, and reasonably sets a network access process under compliance and supervision.
Fig. 7 is a flow chart of a verification of the authentication of a client included in an embodiment of the present invention.
As shown in fig. 7, after a client initiates an authentication application, a system acquires historical data information of the client according to the client information, and simultaneously audits newly applied network access data, after the authentication is passed, a small amount of authentication service is performed to complete accuracy verification of private and public bank cards, after the verification is passed, data verification of credit investigation companies (including professional departments such as banks and public security networks) is performed, and when data is abnormal, the application authentication can be converted into manual service to complete the authentication and audit application.
Fig. 8 is a flow chart of a client contract application included in the embodiment of the present invention.
After the client completes the authentication application, the cloud account member system sends a signing application process, different protocol signing versions are provided through a business system (such as financing, wallet, insurance, fund consumption and the like) of client network access, the purpose of client fast network access is achieved, and the cloud account member system models a signing protocol and a client of the signing protocol, namely a protocol model and a role model.
FIG. 9 is a functional block diagram of a client role model included in an embodiment of the present invention.
As shown in fig. 9, the client role model function diagram is the core content of the cloud account member system, that is, originally scattered and messy client information is unified and integrated into a multi-account model, and unified client member information can be provided through the role model, so that value-added services of thousands of people and thousands of faces are provided for the B/C client, and the internal integrity is guaranteed.
The role model contains four broad categories of attributes: customer attributes, customer account attributes, operator (role) attributes, account attributes.
Customer attributes: when the client applies for network access and completes the functions of different business subsystems (such as financing, purse, insurance, fund withdrawal and the like), the client does not need to apply and verify for authentication for many times, so that the links of repeated verification and authentication in the middle are reduced, and the labor cost is reduced.
Customer account attributes: when a client completes product function applications under different business subsystems (such as financing, wallet, insurance, fund consumption and the like), different business capabilities are provided for the client, different client accounts can be generated, association is achieved, association is reduced, and data confusion caused by data insertion is prevented.
Operator (role) attributes: the user of the client may contain different personnel processes, such as finance, salesman and leaders at different levels, and the management mode of the business is different, so that different operator (role) capabilities are provided, and the client can perform hierarchical management according to the authority after accessing the network.
Account attribute: according to different requirements of customers, combined configuration is carried out, and personalized requirements are met.
To sum up, the application provides a third party payment cloud account member system for there is the member service problem of complicated variety under the different demand backgrounds of numerous trade merchants, this application can carry out the configuration of combination according to customer's different demands, also can export alone, reduces implementation cost, and the entry to the different business of upper strata simultaneously realizes the unified management of customer data. After the cloud account member system is implemented, diversified services can be developed for each subsystem of the payment system by the payment system according to the actual situation of the payment system, customer information under the subsystems of various services in the payment system can be conveniently connected in series, transparency and unification of a customer management processing flow are facilitated, and unified authentication and maintenance management among all service subsystems are achieved.
The embodiments of the present invention have been described in detail, but the embodiments are merely examples, and the present invention is not limited to the embodiments described above. Any equivalent modifications and substitutions to those skilled in the art are also within the scope of the present invention. Accordingly, equivalent changes and modifications made without departing from the spirit and scope of the present invention should be covered by the present invention.
Claims (10)
1. A third party payment cloud account member system is characterized by having a three-layer structure and sequentially comprising a customer service product layer, a customer service information supporting layer and an information centralized processing layer from top to bottom, wherein a lower layer between adjacent layers provides service for an upper layer; wherein the content of the first and second substances,
the customer service product layer is used for providing a uniform entrance, corresponds to a customer service platform, and provides a uniform login center, a personal/enterprise customer center, a protocol center and an authentication registration center according to the service characteristics of third-party payment and aiming at a customer network access mode, so that uniform maintenance is performed in a uniform standard network access mode and a network access protocol;
the client service information supporting layer provides uniform member image service for each service subsystem, corresponds to a client information platform, classifies and normalizes client information acquired by the client service platform, modularly stores information with different attributes, and stores basic information, protocol information, authority information and ciphertext information as required;
the information centralized processing layer corresponds to a client centralized processing platform, and the client centralized processing platform is used for uniformly and modularly managing the information of different clients stored by the client information platform.
2. The member system of claim 1, wherein the third party payment services originate from different service subsystems, and the different service subsystems include any one or more of financing, wallet, insurance, fund and fund consumption.
3. The third party payment cloud account member system of claim 1, wherein the customer service platform comprises one or more of a login center module, a registration authentication center module, a personal customer center module, an enterprise customer center module, a customer contract center module and an open service interface module.
4. The member system of claim 3, wherein the login center module is configured to perform functions including at least one of: ordinary login, trusted login, SSO login, API login, quick login and logout;
the registered authentication center module is configured to realize functions including at least one of the following: registration, information additional recording, activation, personal authentication, enterprise authentication and import authentication;
the personal customer hub module or the enterprise customer hub module configured to perform functions including at least one of: password service, information maintenance, operator management, account logout, security service, operator authority, mobile phone service and login name management;
the client subscription center module is configured to implement functions including at least one of: agreement signing, agreement contract clearing, agreement inquiry and agreement renewal.
5. The third party payment cloud account membership system of claim 1, wherein the customer information platform comprises one or more of a customer identification module, a customer information module, a unified view module, a product account management module, a subscription information module, a quota management module, a rights management module and an information desensitization module.
6. The third party payment cloud account member system of claim 5, wherein the customer information module is configured to store information including one or more of basic information, offline information, authentication information, classification information, asset information, role information, address information, and operation logs;
the authority management module or the quota management module is configured to store information including one or more of client authority, operator authority, account information, product accounts, transaction accumulation, client quota, account quota, and journal;
the signing information module is configured to store information including one or more of signing examples, process configuration, signing main bodies, operation logs, sales plan information and order information;
the information desensitization module is configured to realize one or more functions of desensitization inquiry and desensitization audit.
7. The third party payment cloud account member system of claim 1, wherein the client centralized processing platform comprises one or more of a unified authentication module, a unified profile module, a unified ID module and an information mapping module; wherein the content of the first and second substances,
the uniform authentication module is used for performing uniform authentication and identification on the authenticity of client information for the client accessing the network;
the uniform file module is used for uniformly establishing an account opening protocol file for the client accessing the network aiming at the payment service of each third party and establishing the basic information and the account information of the client when the file is activated;
the uniform ID module is used for uniformly configuring an ID for the client accessing the network;
and the information mapping module is used for mapping the client information to different client accounts through the client role model.
8. The member system of claim 7, wherein the client role model comprises: customer attributes, customer account attributes, operator attributes, account attributes; wherein the content of the first and second substances,
the client attribute is configured to complete authentication and verification after a client applies for network access, so that client basic service is provided for the client;
the client account attribute is configured to provide different service capabilities for the client and generate different client accounts when the client completes product function applications under different service subsystems;
the operator attribute is configured to assign different management authorities to the clients after the clients are accessed to the network;
the account attributes are configured to be combined and configured according to different requirements of customers, and personalized requirements are met.
9. The member system of the third party payment cloud account as claimed in claim 1, further comprising: the main/auxiliary data platform comprises a metadata module, a main data configuration module and an auxiliary data configuration module.
10. The member system of the third party payment cloud account as claimed in claim 1, further comprising: the universal technology platform comprises a universal integration module, a universal query module, a near-end access module and a data consistency module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111402417.7A CN114372788A (en) | 2021-11-24 | 2021-11-24 | Third party payment cloud account member system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111402417.7A CN114372788A (en) | 2021-11-24 | 2021-11-24 | Third party payment cloud account member system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114372788A true CN114372788A (en) | 2022-04-19 |
Family
ID=81139116
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111402417.7A Pending CN114372788A (en) | 2021-11-24 | 2021-11-24 | Third party payment cloud account member system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114372788A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115423521A (en) * | 2022-09-05 | 2022-12-02 | 深圳市一页科技有限公司 | Large-batch concurrent payment optimization system and method thereof |
| CN115456645A (en) * | 2022-08-23 | 2022-12-09 | 广东云徙智能科技有限公司 | Member management method, system, equipment and medium for multi-state and multi-membership |
-
2021
- 2021-11-24 CN CN202111402417.7A patent/CN114372788A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115456645A (en) * | 2022-08-23 | 2022-12-09 | 广东云徙智能科技有限公司 | Member management method, system, equipment and medium for multi-state and multi-membership |
| CN115423521A (en) * | 2022-09-05 | 2022-12-02 | 深圳市一页科技有限公司 | Large-batch concurrent payment optimization system and method thereof |
| CN115423521B (en) * | 2022-09-05 | 2023-08-04 | 深圳市一页科技有限公司 | Large-batch concurrent payment optimizing system and method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210042836A1 (en) | Method, Apparatus, and Computer-Readable Medium For Compliance Aware Tokenization and Control of Asset Value | |
| CN114372788A (en) | Third party payment cloud account member system | |
| CN104392299A (en) | Business information processing method and system | |
| US20140172714A1 (en) | System and method for delegating management of a financial transaction account to a designated assistant | |
| WO2017166071A1 (en) | Smart card service system and method | |
| Sravan et al. | Use of blockchain technology in integrating heath insurance company and hospital | |
| CN111861479A (en) | Financial institution client identity recognition method based on block chain and 5G technology | |
| US11922488B2 (en) | Purchase management system and method | |
| Kubach et al. | On the market for self-sovereign identity: Structure and stakeholders | |
| Chukwu et al. | Effects of digital banking on the performance of commercial banks in Nigeria 2010-2019 | |
| CN112308698B (en) | WeChat end loan product management method and system supporting second-level legal person | |
| CN108875407A (en) | For the sensitive information processing method and processing device of financial business, client, data framework | |
| RU2595550C2 (en) | Method and system for providing universal access to service among multiple services | |
| KR101397556B1 (en) | Method for Management Integrated Account through On-Line | |
| CN109615498A (en) | Revenue data method for managing resource, device, equipment, system and medium | |
| KR20020000399A (en) | Bank loan system through internet | |
| JP6726350B1 (en) | Financial transaction processing device and program | |
| CN109767139A (en) | Based on natural person's credit algorithm from media interaction | |
| CN114022166B (en) | Information processing method, device, computer equipment and storage medium | |
| WO2017166049A1 (en) | Smart card service system and method | |
| CN114546872B (en) | Certificate management testing method and device, computer equipment and storage medium | |
| US20240005385A1 (en) | Purchase management system and method | |
| US20150127542A1 (en) | System and method for verbal authorization for fulfillment of a service | |
| CN114003879A (en) | Asset proxy method, device, electronic equipment and storage medium | |
| Saad et al. | A Proposed Framework for Improving Online Banking Transactions Using Blockchain |
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 |