CN111429125B - Account management method and device, storage medium and electronic equipment - Google Patents
Account management method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111429125B CN111429125B CN202010186638.4A CN202010186638A CN111429125B CN 111429125 B CN111429125 B CN 111429125B CN 202010186638 A CN202010186638 A CN 202010186638A CN 111429125 B CN111429125 B CN 111429125B
- Authority
- CN
- China
- Prior art keywords
- account
- information
- quota
- service platform
- request
- 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.)
- Active
Links
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/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/108—Remote banking, e.g. home banking
-
- 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/22—Payment schemes or models
-
- 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/38—Payment protocols; Details thereof
- G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
-
- 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
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application provides an account management method, an account management device, a storage medium and electronic equipment. The account management method provided by the embodiment of the application comprises the following steps: acquiring limit agreement information sent by a service platform, wherein the limit agreement information comprises account information and preset limit information, and the preset limit information is used for limiting the amount of an account; and determining a calling protocol according to the limit agreement information, so that the account quota management system responds to an account processing request initiated by the service platform according to the quota calling protocol, wherein the account processing request is used for changing the quota information corresponding to the account information in the service platform. The account management method provided by the embodiment of the application realizes the modularization of the account quota management system, so that when a service platform needs a service system with a quota function, the quota system does not need to be developed additionally, and a large amount of repeated development work performed by manpower and material resources is saved.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to an account management method, an account management device, a storage medium, and an electronic device.
Background
With the current development of internet technology, electronic payment has rapidly evolved, meaning that more and more transactions are no longer being conducted off-line. To limit payments, account limits are typically set, such that a given account is limited according to risk management of a particular business or self business requirements.
Currently, existing account quota management systems are typically highly coupled to business systems, requiring separate account quota management systems to be developed independently for each business system. While the primary quota function of an account quota management system typically requires confirmation of a quota account and a quota range. Specifically, for the confirmation of the quota account, the confirmation may be according to a specific service model, for example: user account number, user identification number, user card number, usage channel, etc. And the limit range can be determined according to different services, and the limit of the single amount, the daily amount, the month amount, the year amount, the life amount, the number and the amount of the custom starting and ending time can be independently set.
However, in the process of implementing the application, the inventor finds that because the account limit management system needs to be separately integrated and developed for different service systems, the service system needs to consume a great deal of manpower and material resources to perform repeated development work when accessing the account limit management function.
Disclosure of Invention
The embodiment of the application provides an account management method, an account management device, a storage medium and electronic equipment, which are used for solving the problem that a service system needs to consume a great deal of manpower and material resources to carry out repeated development work when accessing an account quota management function.
In a first aspect, an embodiment of the present application provides an account management method, applied to an account quota management system, including:
Acquiring limit agreement information sent by a service platform, wherein the limit agreement information comprises account information and preset limit information, and the preset limit information is used for limiting the amount of the account;
And determining a calling protocol according to the restriction agreement information, so that the account quota management system responds to an account processing request initiated by the service platform according to the calling protocol, wherein the account processing request is used for changing the quota information corresponding to the account information in the service platform.
In one possible design, after said determining the calling protocol according to said constraint protocol information, the method further comprises:
Acquiring a contract modification request sent by the service platform, wherein the contract modification request comprises new constraint agreement information;
And updating preset limit information in the calling protocol according to the new limit agreement information.
In one possible design, the account information is any one account information in the service platform or all account information in the service platform.
In one possible design, the account processing request includes any one or more of a billing request, a cancellation request, and a quota query request.
In one possible design, after said determining the calling protocol according to said constraint protocol information, the method further comprises:
acquiring the accounting request, wherein the accounting request comprises account information to be accounted and an amount to be accounted;
if a calling protocol corresponding to the account information to be billed exists, acquiring the residual amount corresponding to the account information to be billed;
If the amount to be billed is smaller than the residual amount, sending billing failure information, wherein the billing failure information is used for indicating the service platform to stop payment operation;
And if the amount to be billed is greater than or equal to the residual amount, sending billing success information, wherein the billing success information is used for indicating the service platform to continue payment operation.
In one possible design, after the sending of the accounting success information, the method further includes:
Acquiring the cancellation request, wherein the cancellation request comprises account information to be cancelled and the amount to be cancelled;
and according to the amount to be offset, offset processing is carried out on the residual amount corresponding to the account information to be offset.
In one possible design, the calling protocol includes time range information and limit information corresponding to the time range information, where the time range information and the limit information corresponding to the time range information are determined according to the limit agreement information.
In one possible design, the calling protocol includes multiple layers of sub-nodes, the multiple layers of sub-nodes form a tree structure, wherein each layer of sub-nodes includes account information and preset limit information;
When the account quota management system responds to an account processing request initiated by the service platform according to the calling protocol, the smallest preset quota from a first leaf node to a root node in the calling protocol is selected as a quota corresponding to the account processing request, and the first leaf node is a child node corresponding to the account processing request.
In one possible design, when the account processing request includes a billing request, performing billing processing on a first sub-node, a root node and all sub-nodes between the first sub-node and the root node corresponding to account information to be billed according to the account information to be billed and an amount to be billed in the billing request; or alternatively
When the account processing request comprises a billing request, according to account information to be offset and the amount to be offset in the billing request, performing offset processing on a second sub-node, a root node and all sub-nodes between the second sub-node and the root node corresponding to the account information to be offset.
In one possible design, for each of the account processing request records corresponding account processing record information including an account processing request type identifier.
In a second aspect, an embodiment of the present application provides an account management apparatus, including:
The system comprises an acquisition module, a service platform and a control module, wherein the acquisition module is used for acquiring limit agreement information sent by the service platform, the limit agreement information comprises account information and preset limit information, and the preset limit information is used for limiting the amount of the account;
And the processing module is used for determining a calling protocol according to the limit agreement information so that the account management system responds to an account processing request initiated by the service platform according to the calling protocol, wherein the account processing request is used for changing the amount information corresponding to the account information in the service platform.
In one possible design, the obtaining module is further configured to obtain a contract modification request sent by the service platform, where the contract modification request includes new constraint agreement information;
The processing module is further configured to update preset restriction information in the call protocol according to the new restriction agreement information.
In one possible design, the account information is any one account information in the service platform or all account information in the service platform.
In one possible design, the account processing request includes any one or more of a billing request, a cancellation request, and a quota query request.
In one possible design, the obtaining module is further configured to obtain the accounting request, where the accounting request includes account information to be accounted and an amount to be accounted;
The acquisition module is further used for acquiring the residual amount corresponding to the account information to be billed;
the account management device further includes:
the sending module is used for sending accounting failure information, wherein the accounting failure information is used for indicating the service platform to stop payment operation;
The sending module is further configured to send accounting success information, where the accounting success information is used to instruct the service platform to continue payment operation.
In one possible design, the obtaining module is further configured to obtain the cancellation request, where the cancellation request includes account information to be cancelled and an amount to be cancelled;
And the processing module is also used for conducting cancellation processing on the residual amount corresponding to the account information to be cancelled according to the amount to be cancelled.
In one possible design, the calling protocol includes time range information and limit information corresponding to the time range information, where the time range information and the limit information corresponding to the time range information are determined according to the limit agreement information.
In one possible design, the multiple layers of child nodes form a tree structure, wherein each layer of child nodes comprises account information and preset limit information;
When the account quota management system responds to an account processing request initiated by the service platform according to the calling protocol, the smallest preset quota from a first leaf node to a root node in the calling protocol is selected as a quota corresponding to the account processing request, and the first leaf node is a child node corresponding to the account processing request.
In one possible design, when the account processing request includes a billing request, performing billing processing on a first sub-node, a root node and all sub-nodes between the first sub-node and the root node corresponding to account information to be billed according to the account information to be billed and an amount to be billed in the billing request; or alternatively
When the account processing request comprises a billing request, according to account information to be offset and the amount to be offset in the billing request, performing offset processing on a second sub-node, a root node and all sub-nodes between the second sub-node and the root node corresponding to the account information to be offset.
In one possible design, for each of the account processing request records corresponding account processing record information including an account processing request type identifier.
In a third aspect, an embodiment of the present application further provides an electronic device, including:
A processor; and
A memory for storing executable instructions of the processor;
wherein the processor is configured to perform any one of the possible account management methods of the first aspect via execution of the executable instructions.
In a fourth aspect, embodiments of the present application also provide a storage medium having stored thereon a computer program which when executed by a processor implements any one of the possible account management methods of the first aspect.
According to the account management method, the device, the storage medium and the electronic equipment, the account quota management system is assembled, and when the service platform needs to be accessed with a quota function, the account quota management system can determine a quota calling protocol according to the limit agreement information, so that the service platform can respond to an account processing request initiated by the service platform by calling an interface provided by the account quota management system, and the account quota management system can change the quota information corresponding to the account information in the service platform according to the account processing request. Therefore, a set of account quota management system can be shared for different service platforms, when a new service platform needs a service system with a quota function, the service platform is directly connected to the account quota management system without additional development, and the account quota management system can respond to an account processing request initiated by the service platform according to a quota calling protocol, so that repeated development work which is carried out by the service system with a great deal of manpower and material resources is avoided when the service system is connected to the account quota management function.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions of the prior art, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it will be obvious that the drawings in the following description are some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort to a person skilled in the art.
FIG. 1 is a schematic view of an application scenario of an account management method according to an example embodiment of the present application;
FIG. 2 is a schematic view of an application scenario of an account management method according to another example embodiment of the present application;
FIG. 3 is a flow chart of an account management method according to an example embodiment of the application;
FIG. 4 is a flow chart of an account management method according to another example embodiment of the application;
FIG. 5 is a diagram illustrating an exemplary architecture of a multi-level quota calling protocol in the embodiment shown in FIG. 4;
FIG. 6 is a flow chart of an account management method according to yet another example embodiment of the application;
FIG. 7 is a schematic diagram of an account management device according to an example embodiment of the present application;
fig. 8 is a schematic structural view of an electronic device according to an exemplary embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations 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.
With the continued development of internet technology, electronic payments have evolved rapidly, meaning that more and more transactions are no longer being conducted off-line. To limit payments, account limits are typically set, such that a given account is limited according to risk management of a particular business or self business requirements.
Currently, existing account management systems, such as: the account quota management system is typically highly coupled to the business systems, and a separate account quota management system needs to be developed independently for each business system. While the primary quota function of an account quota management system typically requires confirmation of a quota account and a quota range. Specifically, for the confirmation of the quota account, the confirmation may be according to a specific service model, for example: user account number, user identification number, user card number, usage channel, etc. And the limit range can be determined according to different services, and the limit of the single amount, the daily amount, the month amount, the year amount, the life amount, the number and the amount of the custom starting and ending time can be independently set.
But because account quota management systems are all required to be developed separately and integrated for different business systems. Therefore, in the prior art, for each service system requiring a quota function, when the service system is developed, one quota system needs to be integrally developed at the same time, so that a great deal of manpower and material resources are required to be consumed for repeated development work when the current service system is accessed to an account quota management function.
In the existing account quota mode, when the range of a quota account is modified, a quota system which is integrally developed needs to be modified independently to update functions, when a service has a hierarchy quota, the service needs to call for a plurality of times, and if one account fails to account, the account which is successfully billed needs to be recovered. Moreover, the system operation condition cannot be well monitored without perfect statistical functions.
In view of the above-mentioned problems, the present application provides an account management method, when a service platform needs to access a quota function, after the service platform and an account quota management system are established, the account quota management system directly generates a quota calling protocol according to constraint protocol information by calling an interface provided by the account quota management system, so as to provide quota service for the service platform. Therefore, a set of account quota management system can be shared for different service systems, and when a new service platform needs a service system with a quota function, the account quota management system can respond to an account processing request initiated by the service platform according to a quota calling protocol by directly accessing the account quota management system without developing the quota system. And further, repeated development work which is carried out by consuming a great amount of manpower and material resources when the service system accesses the account quota management function is avoided.
Fig. 1 is a schematic view of an application scenario of an account management method according to an exemplary embodiment of the present application. As shown in fig. 1, in this embodiment, when the service platform (caller server 100) needs to access the quota function, a system access file may be generated first, where the system access file may include attribute information of the service platform (for example, an allocated platform number and a related function description of the system), service platform hierarchy information, service platform default configuration information, and a sample that may be used to test the service platform. After the account quota management system (quota server 200) obtains the system access file generated by the service platform, the platform number can be configured for the service platform in the account quota management system, so that the connection between the service platform and the account quota management system is established.
Fig. 2 is a schematic view of an application scenario of an account management method according to another exemplary embodiment of the present application. As shown in fig. 2, in order to enable a restriction function for a specific service in a service platform, a terminal device (e.g., a personal computer 310 or a smart phone 320) may transmit restriction agreement information to the service platform (caller server 100). For example, when the quota function for a specific service in the service platform is to be implemented, the limitation agreement information may be quota contract information, and specifically, the quota contract information includes account information and preset quota information. Then, the service platform (the caller server 100) sends the quota contract information to the account quota management system (the quota server 200), so that the account quota management system determines a quota calling protocol according to the quota contract information, and the account quota management system responds to an account processing request initiated by the service platform according to the quota calling protocol, wherein the account processing request is used for changing the quota information corresponding to the account information in the service platform, and the account processing request can be, for example, a billing request, a cancellation request and a quota query request. When the account processing request is a billing request, the account quota management system processes the billing request according to a quota calling protocol so as to perform billing processing in the account quota management system, thereby updating the quota information corresponding to the account information in the service platform.
Therefore, the account management method provided by the embodiment is used for assembling the account quota management system, when the service platform needs to be accessed with the quota function, the service platform and the account quota management system are built, and then the account quota management system directly generates a quota calling protocol according to quota contract information by calling an interface provided by the account quota management system, so that the quota service is provided for the service platform. Therefore, a set of account quota management system can be shared for different service systems, and when a new service platform needs a service system with a quota function, the account quota management system can respond to an account processing request initiated by the service platform according to a quota calling protocol by directly accessing the account quota management system without developing the quota system. And further, repeated development work which is carried out by consuming a great amount of manpower and material resources when the service system accesses the account quota management function is avoided.
FIG. 3 is a flow chart of an account management method according to an example embodiment of the application. As shown in fig. 3, the account management method provided in this embodiment includes:
and step 101, obtaining the restriction agreement information sent by the service platform.
Specifically, the restriction agreement information sent by the service platform may be obtained, where the restriction agreement information includes account information and preset restriction information.
Step 102, determining a quota calling protocol according to the constraint protocol information.
And step 103, responding to the account processing request initiated by the service platform according to the quota calling protocol.
After the account quota management system obtains the quota contract information, a quota calling agreement may be determined from the quota contract information. The quota calling protocol may include account information of the performed quota, a quota amount of the account corresponding to the account information, and a calling interface of the account quota management system called by the service platform, so that when the service platform initiates an account processing request, for example, when the service platform initiates a billing request, a cancellation request or a quota inquiry request, the account quota management system responds to the account processing request initiated by the service platform according to the quota calling protocol, thereby changing the quota information corresponding to the account information in the service platform.
After determining the quota calling agreement according to the quota contract information, a contract modification request sent by the service platform can be obtained, wherein the contract modification request comprises new quota contract information, and preset quota information in the calling agreement is updated according to the new quota contract information.
The account information can be any one, a plurality of account information in the service platform or all account information in the service platform. It should be noted that, the preset quota in the quota contract information may be configured uniformly or in a personalized manner. For example, a uniform quota amount may be configured for all accounts of a first service platform accessed by the account quota management system, and a corresponding quota amount may be configured individually for each account of a second service platform accessed by the account quota management system.
In addition, it should be noted that the quota calling protocol may include time range information and quota information corresponding to each time range information, where the time range information and the limitation information corresponding to the time range information are determined according to quota contract information. The limit information may be a limit number and a limit amount. The quota management system may determine a specific quota of the corresponding account according to the time range information and the quota information in the quota calling protocol. The time range information in the quota calling protocol and the quota information corresponding to each time range information can be modified according to service requirements, for example, the quota information can be determined and modified according to credit conditions of the service platform on the account, and the quota information can be modified according to an adjustment request initiated by a user to the service platform. Specifically, for a single account, any one or more of the following information may be included in the quota call protocol: whether the single transaction amount and the single amount are enabled or not; the number of daily transactions, the daily transaction amount and whether daily transactions are controlled; month trade pen data, month trade amount, month trade enable control; the annual transaction amount, whether the annual transaction is enabled or not, whether the lifetime transaction amount, whether the lifetime transaction is enabled or not, the custom time interval transaction amount data, the custom event interval transaction accumulated amount, and whether the custom interval transaction is controlled or not; according to the requirements of the service, if the service sets the quota to a fixed value, a default quota template function can be used for setting, wherein whether a certain item is started or not can be set; if not, the method is set to be no. And the modification records can be recorded when the existing quota is modified, so that the subsequent query problem can be conveniently used.
In this embodiment, by assembling the account quota management system, when the service platform needs to access the quota function, the account quota management system may determine a quota calling protocol according to the quota contract information, so that the service platform may respond to an account processing request initiated by the service platform by calling an interface provided by the account quota management system, so that the account quota management system may change the quota information corresponding to the account information in the service platform according to the account processing request. Therefore, a set of account quota management system can be shared for different service platforms, when a new service platform needs a service system with a quota function, the service platform is directly connected to the account quota management system without additional development, and the account quota management system can respond to an account processing request initiated by the service platform according to a quota calling protocol, so that repeated development work which is carried out by the service system with a great deal of manpower and material resources is avoided when the service system is connected to the account quota management function. In addition, the time range information in the quota calling protocol can be determined through the quota contract information, and the quota information corresponding to each time range information can be determined according to the service requirements, so that the method is suitable for a service platform or a user to change the service requirements, and the quota in the account can be dynamically adjusted through configuring parameters in the quota contract information.
FIG. 4 is a flow chart diagram of an account management method according to another example embodiment of the application. As shown in fig. 4, the account management method provided in this embodiment includes:
Step 201, obtaining the constraint protocol information sent by the service platform.
Step 202, determining a quota calling protocol according to the constraint protocol information.
And 203, responding to an account processing request initiated by the service platform according to a quota calling protocol.
It should be noted that, the specific implementation manner of step 201 to step 203 in this embodiment may refer to the descriptions in step 101 to step 103 in the embodiment shown in fig. 3, and will not be described herein again.
Step 204, obtaining a billing request.
When the terminal equipment is in a consuming action, a billing request needs to be initiated to the service platform, and the service platform organizes data according to a format required by the account quota management system by calling a relevant interface of the account quota management system, so that the account quota management system obtains the billing request, wherein the billing request comprises account information to be billed and an amount to be billed.
Step 205, if there is a quota calling protocol corresponding to the account information to be billed, acquiring a remaining quota corresponding to the account information to be billed.
After the account quota management system acquires the accounting request, before accounting, whether a quota calling protocol corresponding to the account information to be accounted exists or not is also required to be inquired according to the account information to be accounted. And if a quota calling protocol corresponding to the account information to be billed exists, acquiring the residual quota corresponding to the account information to be billed.
Step 206, judging whether the amount to be billed is greater than or equal to the remaining amount. If the determination result is yes, step 207 is executed, and if the determination result is no, step 208 is executed.
Step 207, sending accounting success information.
Step 208, sending accounting failure information.
If the amount to be billed is smaller than the residual amount, sending billing failure information, wherein the billing failure information is used for indicating the service platform to stop payment operation, and if the amount to be billed is greater than or equal to the residual amount, sending billing success information, and the billing success information is used for indicating the service platform to continue payment operation.
It should be noted that the quota calling protocol may be in the form of a single node (corresponding to a single billing quota), or may be in the form of a plurality of nodes (corresponding to a hierarchy of quota billing). When the account quota management system responds to an account processing request initiated by the service platform according to the quota calling protocol, the smallest preset quota from a first leaf node to a root node in the quota calling protocol is selected as a quota corresponding to the account processing request, and the first leaf node is a child node corresponding to the account processing request.
And when the account processing request comprises a billing request, carrying out billing processing on the first sub-node, the root node and all sub-nodes between the first sub-node and the root node corresponding to the account information to be billed according to the account information to be billed and the amount to be billed in the billing request.
A field may be abstracted for different service accounts to identify a specific account by using an "instance original value", and if the specific account is a multi-level account, the quota protocol maintains data in a tree structure, and the lower node records an ID of the upper node, where the instance original value rule may be: root node instance original value + # symbol + lower instance original value until added to leaf node. FIG. 5 is a diagram illustrating an exemplary architecture of a multi-level quota calling protocol in the embodiment shown in FIG. 4. According to the concrete business, analyzing the business model, abstracting out the account and the hierarchy of the limit, and for the single-layer limit account, the account is as follows: and a parent-child payment service, wherein the quota account is a user ID. Whereas for multi-level limit accounts, for example: the bank card pays the multi-channel accounting business, comprising three layers: the first layer is a specific card number ID; the second layer is: the direct connection or substitution buckle type; the third layer is a specific direct-connection bank code or a substitute buckle channel code. As shown in fig. 5, at level 1, the "instance original value" for the card number may be 402359640037; for level 2, the "instance original value" of the quick payment may be 402359640037#qp, and the "instance original value" of the bankcard payment may be 402359640037#ar; for level 3, the "instance original value" of the direct connection shortcut on the shortcut payment side may be 402359640037#qp#zl, the "instance original value" of the substitute deduction channel 1 on the substitute deduction payment side may be 402359640037#ar_szfs_sz_s_01, the "instance original value" of the substitute deduction channel 2 on the bank card substitute deduction payment side may be 402359640037#ar#ar_szfs_sz_s_02, and the "instance original value" of the substitute deduction channel 3 on the bank card substitute deduction payment side may be 402359640037#ar_szfs_sz_s_s_03.
And if the service is set differently for each quota account, the service is required to set the quota calling protocol before the quota is used for billing. Where different limits may be set for nodes of different tiers if a tier limit is present, the smallest limit entry from the leaf node to the root node is used for billing. For example: the current quota of the deduction channel 3 in the layer 3 is 3 ten thousand, the current quota of the bank card deduction payment in the layer 2 is 4 ten thousand, and the current quota of the card number dimension in the layer 1 is 5 ten thousand, so that the smallest limiting item (3 ten thousand of the current quota of the deduction channel 3 in the layer 3) from the leaf node (the deduction channel 3) to the root node (the card number dimension) serves as the current quota when accounting is carried out.
In the billing process of this embodiment, whether billing is performed by a single transaction or by a hierarchical quota, the service platform may be transferred into a transaction, where the transaction includes key fields such as a service access quota platform number, a transaction amount, a quota instance original value, and then the account quota management system may perform normal billing. And, billing is classified into query-after-billing and real-time billing. When the page display of the business is performed, the minimum sum and pen data synthesized by the account or the hierarchical account are firstly queried according to the platform number, the original value of the quota instance and the like, and are given to the front end for business control, and if the quota is enough, the accounting processing is performed. And for real-time billing, the billing interface is directly called when the service system uses the quota, if the service is successful, the billing interface is normally ended, and if the service is failed, the cancellation interface is called to perform cancellation processing.
If the single-layer quota is used, directly inquiring a finally set quota calling protocol, wherein if the quota calling protocol is not used, whether public default configuration exists can be inquired; if the quota calling protocol exists, the final protocol and quota account information are created.
If it is a hierarchy quota, the instance original value is split according to a separator (typically # number) configured in the protocol, and then each hierarchy of final quota is queried. Inquiring limit account list data according to the final limit list; adding transaction amount and number of strokes to each account data according to the account list data, wherein the date, month, year, life and interval are required to be increased, meanwhile, the date of clearing is required to be updated as the current day, the updating condition is that the number of strokes required to be controlled is increased by 1 to be less than or equal to the limit amount, and the corresponding account amount is increased by the transaction amount of the time to be less than or equal to the corresponding limit amount; and updating the account running water, inserting the account running water into the account running water meter, and carrying out account accumulation zero clearing processing of corresponding day, month, year and custom interval according to whether the clearing time is the same as the billing time or not, and carrying out corresponding statistical record addition. Therefore, if the quota account is a hierarchical account, the service platform only needs to call billing once, and the system automatically records the quota account on other hierarchical accounts according to one transaction, so that the service can conveniently expand the service quota according to the self quota. And, after accounting, the statistics processing is automatically carried out.
If the transaction is offset, the transaction is restored by the sum and the number of the money only on the premise that the original transaction is successfully billed. Fig. 6 is a flow chart of an account management method according to yet another example embodiment of the application. As shown in fig. 6, the account management method provided in this embodiment includes:
Step 301, obtaining the constraint protocol information sent by the service platform.
Step 302, determining a quota calling protocol according to the constraint protocol information.
Step 303, responding to the account processing request initiated by the service platform according to the quota calling protocol.
It should be noted that, the specific implementation manner of step 301 to step 303 in this embodiment may refer to the descriptions in step 101 to step 103 in the embodiment shown in fig. 3, and will not be described herein again.
Step 304, obtaining a cancellation request.
And 305, performing cancellation processing on the residual amount corresponding to the account information to be cancelled according to the amount to be cancelled.
The account limit management system acquires a cancellation request, wherein the cancellation request comprises account information to be cancelled and amount to be cancelled, and the cancellation processing is carried out on the residual amount corresponding to the account information to be cancelled according to the amount to be cancelled.
When the account processing request is a billing request, the second child node, the root node and all child nodes between the second child node and the root node corresponding to the account information to be offset in the billing request are offset according to the account information to be offset and the amount to be offset. Therefore, if the quota account is a hierarchical account, the service platform only needs to call billing once, and the system automatically records the quota account on other hierarchical accounts according to one transaction, so that the service can conveniently expand the service quota according to the self quota. And, after accounting, the statistics processing is automatically carried out. If the transaction is processed, the daily, monthly, yearly and lifelong credit of the original transaction is automatically returned.
Further, on the basis of any of the above embodiments, for each account processing request record corresponding account processing record information, the account processing record information includes an account processing request type identifier. Thus, when the data after accounting is required to be compared with other systems, the data is screened and checked through the account processing request type identifier.
Fig. 7 is a schematic diagram of an account management apparatus according to an exemplary embodiment of the present application. As shown in fig. 7, the account management device 400 provided in this embodiment includes:
The obtaining module 401 is configured to obtain limitation agreement information sent by the service platform, where the limitation agreement information includes account information and preset limitation information, and the preset limitation information is used to limit the amount of the account;
And the processing module 402 is configured to determine a call protocol according to the constraint agreement information, so that the account management system responds to an account processing request initiated by the service platform according to the constraint agreement, where the account processing request is used to change the amount information corresponding to the account information in the service platform.
In one possible design, the obtaining module 401 is further configured to obtain a contract modification request sent by the service platform, where the contract modification request includes new constraint agreement information;
the processing module 402 is further configured to update preset restriction information in the calling protocol according to the new restriction agreement information.
In one possible design, the account information is any one account information in the service platform or all account information in the service platform.
In one possible design, the account processing request includes any one or more of a billing request, a cancellation request, and a quota query request.
In one possible design, the obtaining module is further configured to obtain the accounting request, where the accounting request includes account information to be accounted and an amount to be accounted;
The acquisition module is further used for acquiring the residual amount corresponding to the account information to be billed;
the account management device 400 further includes:
A sending module 403, configured to send accounting failure information, where the accounting failure information is used to instruct the service platform to stop payment operation;
the sending module 403 is further configured to send accounting success information, where the accounting success information is used to instruct the service platform to continue payment operation.
In one possible design, the obtaining module 401 is further configured to obtain the cancellation request, where the cancellation request includes account information to be cancelled and an amount to be cancelled;
The processing module 402 is further configured to cancel the remaining amount corresponding to the account information to be cancelled according to the amount to be cancelled.
In one possible design, the calling protocol includes time range information and limit information corresponding to the time range information, where the time range information and the limit information corresponding to the time range information are determined according to the limit agreement information.
In one possible design, the multiple layers of child nodes form a tree structure, wherein each layer of child nodes comprises account information and preset limit information;
When the account quota management system responds to an account processing request initiated by the service platform according to the quota calling protocol, the smallest preset quota from a first leaf node to a root node in the quota calling protocol is selected as a quota corresponding to the account processing request, and the first leaf node is a child node corresponding to the account processing request.
In one possible design, when the account processing request includes a billing request, performing billing processing on a first sub-node, a root node and all sub-nodes between the first sub-node and the root node corresponding to account information to be billed according to the account information to be billed and an amount to be billed in the billing request; or alternatively
When the account processing request comprises a billing request, according to account information to be offset and the amount to be offset in the billing request, performing offset processing on a second sub-node, a root node and all sub-nodes between the second sub-node and the root node corresponding to the account information to be offset.
In one possible design, for each of the account processing request records corresponding account processing record information including an account processing request type identifier.
The account management device provided in the embodiment shown in fig. 7 may be used to execute the account management method provided in any of the above embodiments, and the specific implementation manner and technical effects are similar, and are not repeated here.
Fig. 8 is a schematic structural view of an electronic device according to an exemplary embodiment of the present application. As shown in fig. 8, an electronic device 500 provided in this embodiment includes:
a processor 501; and
A memory 502 for storing executable instructions of the processor, which may also be a flash memory;
Wherein the processor 501 is configured to perform the steps of the above-described method via execution of the executable instructions. Reference may be made in particular to the description of the embodiments of the method described above.
Alternatively, the memory 502 may be separate or integrated with the processor 501.
When the memory 502 is a device separate from the processor 501, the electronic device 50 may further include:
a bus 503 for connecting the processor 501 and the memory 502.
The present embodiment also provides a readable storage medium having a computer program stored therein, which when executed by at least one processor of an electronic device, performs the methods provided by the various embodiments described above.
The present embodiment also provides a program product comprising a computer program stored in a readable storage medium. The computer program may be read from a readable storage medium by at least one processor of an electronic device, and executed by the at least one processor, causes the electronic device to implement the methods provided by the various embodiments described above.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features can be replaced equivalently; such modifications and substitutions do not depart from the spirit of the application.
Claims (13)
1. An account management method, applied to an account management system, comprising:
Acquiring limit agreement information sent by a service platform, wherein the limit agreement information comprises account information and preset limit information, and the preset limit information is used for limiting the amount of the account;
Determining a calling protocol according to the constraint protocol information, so that the account management system responds to an account processing request initiated by the service platform according to the calling protocol, wherein the account processing request is used for changing the amount information corresponding to the account information in the service platform; the call protocol comprises a call interface of a service platform call account management system, wherein the call interface is used for responding to an account processing request initiated by the service platform; and sharing a set of account quota management system for different service platforms.
2. The account management method according to claim 1, further comprising, after the determination of the call protocol from the restriction agreement information:
Acquiring a contract modification request sent by the service platform, wherein the contract modification request comprises new constraint agreement information;
And updating preset limit information in the calling protocol according to the new limit agreement information.
3. The account management method according to claim 1 or 2, wherein the account information is any account information in the service platform or all account information in the service platform.
4. The account management method of claim 2, wherein the account processing request includes any one or more of a billing request, a cancellation request, and a quota query request.
5. The account management method of claim 4, further comprising, after the determining a calling protocol according to the restriction agreement information:
acquiring the accounting request, wherein the accounting request comprises account information to be accounted and an amount to be accounted;
if a calling protocol corresponding to the account information to be billed exists, acquiring the residual amount corresponding to the account information to be billed;
If the amount to be billed is smaller than the residual amount, sending billing failure information, wherein the billing failure information is used for indicating the service platform to stop payment operation;
And if the amount to be billed is greater than or equal to the residual amount, sending billing success information, wherein the billing success information is used for indicating the service platform to continue payment operation.
6. The account management method of claim 5, further comprising, after the sending of the accounting success information:
Acquiring the cancellation request, wherein the cancellation request comprises account information to be cancelled and the amount to be cancelled;
and according to the amount to be offset, offset processing is carried out on the residual amount corresponding to the account information to be offset.
7. The account management method according to any one of claims 1, 2, or 4 to 6, wherein the calling protocol includes time range information, and restriction information corresponding to the time range information, wherein the time range information and the restriction information corresponding to the time range information are determined according to the restriction agreement information.
8. The account management method according to any one of claims 1,2 or 4-6, wherein the calling protocol includes a plurality of layers of sub-nodes, the plurality of layers of sub-nodes forming a tree structure, wherein each layer of sub-nodes includes account information and preset limit information;
when the account management system responds to an account processing request initiated by the service platform according to the calling protocol, the smallest preset quota from a first leaf node to a root node in the calling protocol is selected as a quota corresponding to the account processing request, and the first leaf node is a child node corresponding to the account processing request.
9. The account management method according to claim 8, wherein when the account processing request includes a billing request, billing processing is performed on a first sub-node, a root node, and all sub-nodes between the first sub-node and the root node corresponding to account information to be billed according to the account information to be billed and an amount to be billed in the billing request; or alternatively
When the account processing request comprises a billing request, according to account information to be offset and the amount to be offset in the billing request, performing offset processing on a second sub-node, a root node and all sub-nodes between the second sub-node and the root node corresponding to the account information to be offset.
10. The account management method of claim 9, wherein for each account processing record information corresponding to the account processing request record, the account processing record information includes an account processing request type identifier.
11. An account management device, comprising:
The system comprises an acquisition module, a service platform and a control module, wherein the acquisition module is used for acquiring limit agreement information sent by the service platform, the limit agreement information comprises account information and preset limit information, and the preset limit information is used for limiting the amount of the account;
The processing module is used for determining a calling protocol according to the limit agreement information so that the account management system responds to an account processing request initiated by the service platform according to the calling protocol, wherein the account processing request is used for changing the amount information corresponding to the account information in the service platform; the call protocol comprises a call interface of a service platform call account management system, wherein the call interface is used for an account processing request initiated by the service platform; and sharing a set of account quota management system for different service platforms.
12. An electronic device, comprising:
A processor; and
A memory for storing a computer program of the processor;
wherein the processor is configured to implement the account management method of any one of claims 1 to 10 by executing the computer program.
13. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the account management method of any of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010186638.4A CN111429125B (en) | 2020-03-17 | 2020-03-17 | Account management method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010186638.4A CN111429125B (en) | 2020-03-17 | 2020-03-17 | Account management method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111429125A CN111429125A (en) | 2020-07-17 |
| CN111429125B true CN111429125B (en) | 2024-04-19 |
Family
ID=71553494
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010186638.4A Active CN111429125B (en) | 2020-03-17 | 2020-03-17 | Account management method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111429125B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113850577A (en) * | 2021-09-24 | 2021-12-28 | 支付宝(杭州)信息技术有限公司 | Resource account processing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108038683A (en) * | 2017-12-08 | 2018-05-15 | 上海壹账通金融科技有限公司 | Method of payment, payment system and readable storage medium storing program for executing based on two class accounts |
| CN108446975A (en) * | 2018-03-28 | 2018-08-24 | 上海数据交易中心有限公司 | A kind of quota control method and device |
| CN109377270A (en) * | 2018-09-29 | 2019-02-22 | 湖南共睹互联网科技有限责任公司 | Transaction ensures platform and its account management-control method, terminal and readable storage medium storing program for executing |
| CN110135984A (en) * | 2019-04-04 | 2019-08-16 | 深圳壹账通智能科技有限公司 | Exchange management method, device, computer equipment and storage medium |
-
2020
- 2020-03-17 CN CN202010186638.4A patent/CN111429125B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108038683A (en) * | 2017-12-08 | 2018-05-15 | 上海壹账通金融科技有限公司 | Method of payment, payment system and readable storage medium storing program for executing based on two class accounts |
| CN108446975A (en) * | 2018-03-28 | 2018-08-24 | 上海数据交易中心有限公司 | A kind of quota control method and device |
| CN109377270A (en) * | 2018-09-29 | 2019-02-22 | 湖南共睹互联网科技有限责任公司 | Transaction ensures platform and its account management-control method, terminal and readable storage medium storing program for executing |
| CN110135984A (en) * | 2019-04-04 | 2019-08-16 | 深圳壹账通智能科技有限公司 | Exchange management method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111429125A (en) | 2020-07-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108446975B (en) | Quota management method and device | |
| CN108427581A (en) | System micro services method and terminal device | |
| CN109325729A (en) | A kind of method and server generating electronic contract | |
| WO2020248883A1 (en) | Debt collection method, system and apparatus | |
| CN106656839A (en) | Resource transfer method and apparatus | |
| CN110347545A (en) | A kind of test method and device of business platform cache policy | |
| CN113205402A (en) | Account checking method and device, electronic equipment and computer readable medium | |
| CN111340639A (en) | Settlement data processing method and device | |
| CN110634066A (en) | Method, device and equipment for determining settlement interest | |
| CN116091258A (en) | Data processing method and device for account checking management | |
| CN109614263B (en) | Disaster tolerance data processing method, device and system | |
| CN111429125B (en) | Account management method and device, storage medium and electronic equipment | |
| CN111831868A (en) | Method and apparatus for financial product configuration | |
| CN111444212A (en) | Unified accounting method and device based on accounting system and accounting system | |
| CN100543720C (en) | Utilize the method and system of discrete unit quick establishing business processing flow | |
| CN111583030B (en) | Payment routing method and device | |
| CN115526699A (en) | Payment fund reconciliation method, device, equipment and computer-readable storage medium | |
| CN115526722A (en) | Method and device for processing transaction of making positive | |
| CN113313424A (en) | Method and device for processing accounting data | |
| CN114186267A (en) | A virtual asset data processing method, device and computer-readable storage medium | |
| CN114493555A (en) | Resource processing method, apparatus, computer equipment and storage medium | |
| CN112819606A (en) | Middle-platform cross-industry point settlement method and system | |
| KR20190090685A (en) | Processing method and apparatus for financial instrument information | |
| CN110971664A (en) | Interface service management system | |
| CN116382924B (en) | Recommendation method and device for resource allocation, electronic equipment and storage medium |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant after: Jingdong Technology Holding Co.,Ltd. Address before: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant before: Jingdong Digital Technology Holding Co.,Ltd. Address after: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant after: Jingdong Digital Technology Holding Co.,Ltd. Address before: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Beijing Economic and Technological Development Zone, 100176 Applicant before: JINGDONG DIGITAL TECHNOLOGY HOLDINGS Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |