CN117710079A

CN117710079A - Account visitor-based account processing method, device, equipment and medium

Info

Publication number: CN117710079A
Application number: CN202311833006.2A
Authority: CN
Inventors: 吴磊
Original assignee: Agricultural Bank of China
Current assignee: Agricultural Bank of China
Priority date: 2023-12-27
Filing date: 2023-12-27
Publication date: 2024-03-15

Abstract

The embodiment of the invention discloses an account processing method, device, equipment and medium based on an account accessor. The method comprises the following steps: determining a target billing scene and a target account type to be settled in response to a billing request of a service module through a unified billing center interface; acquiring a first account accessor to be used according to a target accounting scene; acquiring a second account accessor which needs to be called for the target account type; and combining the first account accessor and the second account accessor to access the target account to be settled so as to call public operation of the target account type and call personalized operation of the target account type in the target accounting scene to obtain an accounting processing result. According to the technical scheme provided by the embodiment of the invention, the accounting processing process is standardized and modeled, so that the accounting processing efficiency is improved.

Description

Account visitor-based account processing method, device, equipment and medium

Technical Field

The embodiment of the invention relates to the technical field of data information processing, in particular to an account processing method, device, equipment and medium based on an account accessor.

Background

The payment settlement system of a bank is an important infrastructure of the bank and provides fund clearing and settlement services for various financial products and different types of bank clients, so that the system processes accounts of a large number of different types of settlement accounts, such as debit cards, checks, passbooks, cash, present draft, credit cards, internal accounts, public settlement accounts, clearing transitional accounts and the like, one type of business usually involves a plurality of types of settlement accounts based on the complexity of banking scenes, and the processing logic of various types of different settlement accounts in the accounting scenes of different transaction contexts can also be different. In addition, transactions associated with payment settlement services will have a life cycle, and different links in the transaction life cycle will trigger different billing processing logic. Therefore, each type of service needs to carry out accounting processing procedures of different account types under different accounting links.

In the prior art, for the processing process of various services, the processing process is often bound and coupled with the transaction link of the current service, and for the account to be processed, different account types are identified through transaction contexts, so that different branch processing logics can be determined. However, when the system is realized, because great differences exist in transaction links of different services, a great deal of repeated redundancy is inevitably generated in each service module or billing processing logic in the same service module, so that maintainability and expansibility of codes are poor, and further, the efficiency of accounting processing is reduced.

Disclosure of Invention

The invention provides an account processing method, device, equipment and medium based on an account accessor, so as to improve the account processing efficiency.

In a first aspect, an embodiment of the present invention provides an account processing method based on an account accessor, where the method includes:

determining a target billing scene and a target account type to be settled in response to a billing request of a service module through a unified billing center interface;

acquiring a first account accessor to be used according to the target accounting scene;

acquiring a second account accessor which needs to be called for the target account type;

and combining the first account accessor and the second account accessor, and accessing the target account to be settled so as to call the public operation of the target account type and call the personalized operation of the target account type in the target accounting scene to obtain an accounting processing result.

In a second aspect, an embodiment of the present invention further provides an accounting processing device based on an account accessor, where the device includes:

the information determining module is used for determining a target billing scene and a target account type to be settled in response to a billing request of the service module through a unified billing center interface;

The first accessor acquisition module is used for acquiring a first account accessor to be used according to the target accounting scene;

the second accessor acquisition module is used for acquiring a second account accessor which is required to be called by the target account type;

the result obtaining module is used for combining the first account accessor and the second account accessor, accessing the target account to be settled, and calling public operation of the target account type and personalized operation of the target account type in the target accounting scene to obtain an accounting processing result.

In a third aspect, an embodiment of the present invention further provides an electronic device, including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform an account accessor-based accounting method of any one of the embodiments of the present invention.

In a fourth aspect, embodiments of the present invention further provide a storage medium containing computer-executable instructions that, when executed by a computer processor, enable the computer processor to perform any one of the account visitor-based accounting methods provided by the embodiments of the present invention.

According to the embodiment of the invention, through a unified billing center interface, a target billing scene and a target account type needing settlement are determined in response to a billing request of a service module; acquiring a first account accessor to be used according to a target accounting scene; acquiring a second account accessor which needs to be called for the target account type; and combining the first account accessor and the second account accessor to access the target account to be settled so as to call public operation of the target account type and call personalized operation of the target account type in the target accounting scene to obtain an accounting processing result. According to the technical scheme provided by the embodiment of the invention, the accounting processing process is standardized and modeled, so that the accounting processing efficiency is improved.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1A is a flow chart of an account accessor-based accounting method according to a first embodiment of the present invention;

FIG. 1B is a schematic diagram of a billing model according to a first embodiment of the invention;

FIG. 2A is a flow chart of another accounting method based on an account accessor according to a second embodiment of the present invention;

FIG. 2B is a schematic diagram of a billing center class diagram according to a second embodiment of the invention;

fig. 2C is a schematic diagram of an account type diagram according to a second embodiment of the present invention;

FIG. 2D is a schematic diagram of an account accessor class diagram according to a second embodiment of the present invention;

FIG. 2E is a schematic diagram of a billing object access relationship provided in accordance with a second embodiment of the invention;

fig. 3 is a schematic structural diagram of an accounting processing device based on an account accessor according to a third embodiment of the present invention;

fig. 4 is a schematic structural diagram of an electronic device according to an accounting method based on an account accessor according to a fourth embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures 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 invention 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.

In addition, it should be noted that, in the technical scheme of the invention, the related processes of collection, storage, use, processing, transmission, provision, disclosure and the like of the related data and the like all conform to the regulations of related laws and regulations and do not violate the popular regulations.

Example 1

Fig. 1A is a flowchart of an account visitor based accounting processing method according to an embodiment of the present invention, where the method may be applicable to normalization of accounting processing, and the method may be performed by an account visitor based accounting processing device, where the account visitor based accounting processing device may be implemented in hardware and/or software, and where the account visitor based accounting processing device may be configured in an electronic device, where the electronic device may be a terminal device or a server, and the embodiment of the present invention is not limited thereto.

As shown in fig. 1A, fig. 1B is a schematic structural diagram of an accounting model provided according to a first embodiment of the present invention, which specifically includes the following steps:

s110, determining a target billing scene and a target account type to be settled in response to a billing request of the service module through a unified billing center interface.

In particular, the billing center interface may be specifically understood as centralized management of billing actions for transactions of different traffic types, where actions including but not limited to triggering billing actions in payment settlement services may be described and defined in an abstract manner and provided with billing context entries of various standards. In response to the billing request of the service module, a target billing scene in which the billing request is located and a target account type to be settled can be determined through a unified billing center interface.

Wherein, the billing scene includes but is not limited to information input, information confirmation, account verification and account verification initiated by the counter, it is understood that corresponding billing actions are different for different billing scenes, and the specific inclusion type of the billing scene is not limited in the embodiment of the invention; account types include, but are not limited to, debit cards, passbooks, cash, and embodiments of the invention do not limit the specifics of the account type.

After responding to the billing request of the service module, the corresponding billing scene and the target account type needing to be settled can be determined through a unified billing center interface according to the billing request, so that follow-up work can be carried out according to the acquired information.

S120, acquiring a first account accessor to be used according to the target accounting scene.

S130, acquiring a second account accessor which needs to be called by the target account type.

Specifically, according to the acquired target billing scene, a corresponding first account accessor to be used can be acquired; and according to the acquired target account type, acquiring a second account accessor needing to be called. That is, according to the acquired target billing scene, the first account accessor required to be used in the billing scene can be determined; based on the obtained target account type, a second account accessor required to be selected in the account type can be determined. The embodiment of the invention does not limit the acquisition modes of the first account accessor and the second account accessor.

After the first account accessor to be used is obtained according to the target accounting scene and the second account accessor to be called is obtained according to the target account type, the follow-up operation is conveniently carried out according to the obtained first account accessor and the second account accessor.

S140, combining the first account accessor and the second account accessor, and accessing the target account to be settled so as to call public operation of the target account type and call personalized operation of the target account type in the target accounting scene to obtain an accounting processing result.

Specifically, by combining the acquired first account accessor and second account accessor, the target account to be settled can be accessed, the public operation of the target account type is called, the personalized operation of the target account type in the target accounting scene is called, and the corresponding accounting processing result can be obtained.

It may be understood that the common operation of the target account types may be a common operation that needs to be performed for any target account. So that the system can only call the income and expense processing logic of the settlement account associated with the transaction when the system carries out accounting processing on the settlement account of the same class in different businesses. Illustratively, the public operation of the target account type includes, but is not limited to, inputting an account password corresponding to the target account, and the embodiment of the invention does not limit contents included in the public operation of the target account type;

The individualization of the target account type in the target billing scene may be understood as the operations to be performed in different target billing scenes are different for the same target account type. Corresponding personalized operations can be executed for the same type of settlement accounts under different transaction context accounting scenes, and the separation and flexible superposition combination of difference logics can be realized through the personalized behaviors of different account accessors. The same account type can call different account accessors to conduct personalized processing in different billing scenes. Thus, the target account type is personalized in the target billing scenario, that is to say the operations that need to be selected and performed for the particular target account type in the target billing scenario.

Specifically, the target account to be settled is accessed, the public operation of the target account type is called, the personalized operation of the target account type in the target accounting scene is called, and the corresponding accounting processing result can be obtained. By distinguishing the public operation and the personalized operation of the target account types, the same public operation can be conveniently called when different target account types are executed, and the personalized operation corresponding to the corresponding target account types is called.

In the technical solution provided in this embodiment, different service types may be abstracted into one billing model, and in particular, for different service types, a billing center corresponding to the service type may be constructed. The billing model may be composed of a billing scene, an account accessor, and various types of settlement account objects, see FIG. 1B for details. It should be noted that, in the billing model, each type of account may be defined as a basic entity, where the account may have public operations and personalized operations under different billing scenarios, where only public operations related to the account's own billing may be implemented by the billing account object, personalized operations related to the specific billing scenario of the current module may be stored in the billing center, for personalized operations already stored in the account accessor, operations that may be multiplexed in two or more modules or scenarios may be performed, and for public operations stored in the account accessor, operations that may be performed by all modules as auxiliary supplementary accounts that may be multiplexed. That is, for personalization operations, it is necessary to implement the process under a specific billing scenario and through a corresponding account accessor.

Example two

Fig. 2A is a flowchart of another accounting processing method based on an account accessor according to a second embodiment of the present invention, where the technical solution of the embodiment of the present invention is further optimized based on the foregoing alternative technical solutions.

Further, the method further refines the steps of determining a target billing scene and a target account type to be settled in response to a billing request of a service module through a uniform billing center interface into the steps of determining a billing mode, an account to be settled and a transaction link in response to the billing request of the service module through the uniform billing center interface; selecting a target billing scene from the candidate billing scenes according to the billing mode and the transaction link; and determining the type of the target account to be settled according to the account to be settled so as to improve the accounting processing efficiency. It should be noted that, in the present embodiment, parts not described in the present embodiment may refer to the related expressions of other embodiments, which are not described herein.

As shown in fig. 2A, fig. 2B is a schematic structural diagram of a billing center class diagram according to a second embodiment of the present invention, fig. 2C is a schematic structural diagram of an account type diagram according to a second embodiment of the present invention, fig. 2D is a schematic structural diagram of an account accessor class diagram according to a second embodiment of the present invention, and fig. 2E is a schematic structural diagram of a billing object access relationship according to a second embodiment of the present invention, which specifically includes the following steps:

s210, determining a billing mode, an account to be settled and a transaction link in response to a billing request of the service module through a unified billing center interface.

Specifically, after responding to the billing request of the service module, the billing mode, the account to be settled and the transaction link corresponding to the service module can be determined through a unified billing center interface. In particular, the embodiment of the invention does not limit the determination mode of determining the billing mode, the account to be settled and the transaction link according to the billing center interface.

It should be noted that, the accounting center class diagram is detailed in fig. 2B, when defining an accounting center interface, a standard accounting scene and a scene matching operation entry can be defined in the interface, and an existing accounting center implementation class can be implemented or multiplexed according to actual situations for different services.

Based on the billing request of the service module, the billing mode, the account to be settled and the transaction link can be determined through a unified billing center interface so as to facilitate the development of subsequent work according to the acquired information.

S220, selecting a target billing scene from the candidate billing scenes according to the billing mode and the transaction link.

S230, determining the type of the target account to be settled according to the account to be settled.

Specifically, based on the acquired billing mode and transaction link, a corresponding target billing scene can be selected from the candidate billing scenes; the type of target account to be settled may be determined based on the account to be settled. In particular, the selection manner of the target billing scene and the determination manner of the target account type are not limited in the embodiment of the invention.

Optionally, the target account object corresponding to the target account type includes a basic operation interface and a public operation interface to be called; the basic operation interface comprises at least one of the following: a checkout interface, a payment interface, an expiration date interface, or an entry of input data; and the public operation interface is an operation interface for dynamically binding and calling the account accessor for the target account type.

Specifically, the target account object corresponding to the target account type comprises a basic operation interface and a public operation interface to be called. The basic operation interface comprises at least one of a collection interface, a payment interface, an effective date interface or an input data entry, and the type of the interface included in the basic operation interface is not limited in the embodiment of the invention; the public operation interface may be an operation interface for dynamically binding and calling the account accessor by the target account type, that is, the public operation interface is not limited to the billing scenario, and the public operation may be an operation that can be multiplexed in all modules.

S240, acquiring a first account accessor to be used according to the target accounting scene.

Specifically, according to the acquired target accounting scene, the first account accessor to be used can be acquired, and the acquisition mode of the first account accessor is not limited in the embodiment of the invention.

Optionally, according to the target billing scenario, acquiring a first account accessor to be used includes: matching the target billing scene with the dynamic binding relation between the candidate billing scene and the candidate account accessor, and taking the candidate account accessor dynamically bound by the target billing scene as a first account accessor to be used; the candidate billing scene, the candidate account accessor or the dynamic binding relation is predetermined according to the settlement requirement of the service module.

Specifically, when the first account accessor to be used is obtained according to the target accounting scene, the first account accessor can be matched with the target accounting scene based on the dynamic binding relationship between the candidate accounting scene and the candidate account accessor, and the candidate account accessor dynamically bound with the target accounting scene is used as the first account accessor to be used. It should be noted that, the candidate billing scenario, the candidate account visitor, or the dynamic binding relationship may be predetermined according to the settlement requirement of the service module, which is not limited in the embodiment of the present invention.

In particular, a standard Account type interface IAccount, and Account abstract class may be defined, while Account attributes associated with an Account may be bound and a call interface may be provided to bind an Account accessor, see FIG. 2C for details.

Matching the target billing scene with the dynamic binding relation between the candidate billing scene and the candidate account accessor, and taking the candidate account accessor dynamically bound with the target billing scene as a first account accessor to be used; wherein the candidate billing scene, the candidate account accessor or the dynamic binding relationship is predetermined according to the settlement requirement of the service module. According to the method, according to the target billing scene, the more accurate first account accessor to be used is conveniently obtained, and development of subsequent steps is facilitated.

S250, acquiring a second account accessor which needs to be called by the target account type.

Specifically, a second account accessor that the target account type needs to call may be obtained.

Optionally, the second account accessor includes a common account accessor for encapsulating the operation of each account type in common under each billing scenario.

Specifically, the second account accessor comprises a public account accessor which can be used for packaging the general operation of each account type in each billing scene. That is, multiple types of settlement accounts may be accessed separately for any account accessor, and operations common to all settlement accounts and all billing scenarios may be packaged in a common account accessor.

It is noted that at least one common account accessor component may be reused for different billing scenarios in the billing center. In addition, for any account accessor object, an access interface for different types of settlement accounts is provided, wherein operations related to the types of settlement accounts related to the transaction should be provided all, and the access interfaces for settlement accounts not related to the transaction can be implemented empty, which is not limited by the embodiment of the invention.

The second account accessor comprising the common account accessor can be used for packaging the general operation of each account type under each billing scene by acquiring the required call of the target account type. The method is convenient for standardizing and modeling the general operation of each account type in each billing scene, and further facilitates the subsequent call of the related general operation.

S260, combining the first account accessor and the second account accessor, and accessing the target account to be settled so as to call public operation of the target account type and call personalized operation of the target account type in the target accounting scene to obtain an accounting processing result.

Specifically, the first account accessor and the second account accessor are combined to access the target account to be settled, and the accounting processing result can be obtained by calling the public operation of the target account type and calling the personalized operation of the target account type in the target accounting scene. That is, in any accounting scenario of the accounting center, the first account accessor and the second account accessor may be combined, and access is performed to a specific target account to be settled according to the combined account accessor, so as to implement call to the target account, and when call to the target account, an exemplary operation may be that a collection action, a payment action or a corresponding action on the target account is called, so as to complete an accounting processing task in a specific accounting scenario, so as to obtain a corresponding accounting processing result.

Optionally, combining the first account accessor and the second account accessor, accessing a target account to be settled, so as to call public operation of a target account type and call personalized operation of the target account type in a target accounting scene to obtain an accounting processing result, including: and calling a corresponding second account accessor through the target account type to execute public operation corresponding to the target account type, and executing personalized operation of the target account type under the target accounting scene through the first account accessor to obtain an accounting processing result.

Specifically, when the accounting processing result is obtained, the corresponding second account accessor can be called through the target account type to execute the public operation corresponding to the target account type, and the first account accessor is used for executing the personalized operation of the target account type in the target accounting scene to obtain the accounting processing result.

In particular, the account accessor class diagram is detailed in FIG. 2D, where all account types are accessible to any account accessor. Wherein CM, BP, books, CS, AI refers to different account types that are accessible; the target account type may be a common behavior initiated by the terminal channel counter, automatically processed by the Auto system, invocable by ALL accounts of ALL (recording current channel, current equipment), and RElsys management system (payment in line-invoked by other business modules such as online bank or loan), which the embodiments of the present invention do not limit. It should be noted that during this process, the account accessor may be dynamically added, and the existing code structure is not required to be changed, and for example, when the demand of adding the account accessor is responded, the account accessor may be added, and the accounts under different account types may be accessed through the visit () method.

It should be noted that, the process of calling the public operation of the target account type and the operation of the accounting accessor may be iterated, and the public operation of a specific account type may be continuously encapsulated into the corresponding account type, so as to gradually iterate and extract the reusable differential operation/common operation related to different accounts and different transaction scenes into the account accessors of the corresponding scene participants. Under any accounting scene of the accounting center, different account accessors can be combined to access specific settlement accounts so as to call account access operation on account types, and therefore accounting processing of specific accounting scenes of corresponding services is completed.

Particularly, under the condition of acquiring the new account type, determining a public operation required to be executed by the new account type, determining whether a candidate account accessor for executing the public operation exists, and if so, constructing an association relationship between the new account type and a corresponding candidate account accessor; and determining a billing scene to which the new account type belongs, and personalizing the new account type in the billing scene to which the new account type belongs, determining whether a candidate account accessor for executing the personalizing operation exists, and if so, constructing an association relationship between the new account type and the corresponding candidate account accessor under the billing scene to which the new account type belongs. If there is no candidate account accessor for executing the public operation or the personalized operation, the account accessor is newly added.

In addition, the method can also be used for adding the account scene to which any account type belongs, determining the personalized operation of the account type in the added account scene, determining whether a candidate account accessor for executing the personalized operation exists, and if so, constructing the association relationship between the personalized operation of the account type in the added account scene and the corresponding candidate account accessor. If there is no candidate account accessor for executing the personalized operation, the account accessor is added.

In particular, in the billing object access relationship, according to different transfer modes and transaction links, corresponding billing scenes can be matched in the billing center, specific account types can be obtained in corresponding billing scene interfaces, and different account accessors can be bound through dynamic combination, so that the account access processing on the specific account types can be finally realized, and details are shown in fig. 2E. The transfer mode includes, but is not limited to, different fund source accounts, different collection verification types, and the embodiment of the invention is not limited to this.

In an alternative embodiment, the accounting scenario of the real-time debit service is illustrated with respect to fig. 2E, which is an example of a subsequent accounting process to be performed after receiving payment from the other party.

The technical scheme provided by the embodiment of the invention is exemplified by a bank-size payment system, and the processing ideas of the payment settlement in the bank system, the cross-border RMB payment settlement and other payment settlement systems are similar to those provided by the embodiment of the invention, so that the technical scheme provided by the embodiment of the invention can be referred to, and the details are not repeated here.

The accounting processing logic of various payment settlement services is realized by standardizing the accounting scene of the conventional payment settlement services of the bank, taking the standardized accounting scene as an entrance, flexibly combining different account accessors to access various settlement account entities, and triggering the account depositing and withdrawing processing of various settlement accounts according to the payment and receiving scene. The main advantages are as follows: (1) The billing process of the payment settlement business is standardized, modeled and standardized; (2) The reusability of the billing process and the capability of disassembling complex billing logic are improved. The complex billing logic is decomposed layer by separating core field objects in the billing process, different transaction contexts (which accessors need to be bound) in the billing process, different transaction billing links and reusable difference behaviors of different settlement accounts-account accessors and common behaviors are extracted, a billing processing model which can be flexibly combined is formed for multiplexing of different services, and the code redundancy of billing processing is greatly reduced; (3) The billing model has strong adaptability and self-accumulation capacity, and can realize continuous improvement of the billing model by continuous iteration and precipitation of each layer of core objects in the model, and continuously perform convergence iteration on each layer of objects in the model in various billing processes. Forming a model hierarchical structure with a stable base and a flexible upper layer; (4) The method has strong expansibility, and can dynamically add new or perfect existing billing center objects, account accessor objects and account objects according to the specific business scenes in the future, thereby realizing the model arrangement of the new business billing process.

According to the embodiment of the invention, a billing mode, an account needing to be settled and a transaction link are determined in response to a billing request of a service module through a unified billing center interface; selecting a target billing scene from the candidate billing scenes according to the billing mode and the transaction link; determining a target account type to be settled according to the account to be settled; matching the target billing scene with the dynamic binding relation between the candidate billing scene and the candidate account accessor, and taking the candidate account accessor dynamically bound by the target billing scene as a first account accessor to be used; the candidate billing scene, the candidate account accessor or the dynamic binding relation is predetermined according to the settlement requirement of the service module. And acquiring a second account accessor which needs to be called by the target account type, wherein the second account accessor comprises a public account accessor and is used for packaging the general operation of each account type under each billing scene. And calling a corresponding second account accessor through the target account type to execute public operation corresponding to the target account type, and executing personalized operation of the target account type under the target accounting scene through the first account accessor to obtain an accounting processing result. According to the technical scheme provided by the embodiment of the invention, the accounting processing process is standardized and modeled, so that the accounting processing efficiency is improved.

Example III

Fig. 3 is a schematic structural diagram of an accounting processing device based on an account accessor according to a third embodiment of the present invention. As shown in fig. 3, the account processing device based on the account accessor includes: an information determination module 310, a first accessor acquisition module 320, a second accessor acquisition module 330, and a result acquisition module 340. Wherein:

an information determining module 310, configured to determine, through a unified billing center interface, a target billing scenario in which a billing request of a service module is located and a target account type to be settled;

a first accessor obtaining module 320, configured to obtain a first account accessor to be used according to the target accounting scenario;

a second accessor obtaining module 330, configured to obtain a second account accessor that needs to be called by the target account type;

and the result obtaining module 340 is configured to combine the first account accessor and the second account accessor, and access the target account to be settled, so as to invoke a public operation of the target account type and invoke a personalized operation of the target account type in the target accounting scene to obtain an accounting processing result.

Optionally, the first accessor obtaining module 320 is specifically configured to:

matching the target billing scene with the dynamic binding relation between the candidate billing scene and the candidate account accessor, and taking the candidate account accessor dynamically bound by the target billing scene as a first account accessor to be used; the candidate billing scene, the candidate account accessor or the dynamic binding relation is predetermined according to the settlement requirement of the service module.

Optionally, the result obtaining module 340 is specifically configured to:

and calling a corresponding second account accessor through the target account type to execute public operation corresponding to the target account type, and executing personalized operation of the target account type under the target accounting scene through the first account accessor to obtain an accounting processing result.

Optionally, the information determining module 310 includes:

the billing information determining unit is used for determining a billing mode, an account needing settlement and a transaction link in response to a billing request of the service module through a unified billing center interface;

the billing scene selection unit is used for selecting a target billing scene from the candidate billing scenes according to the billing mode and the transaction link;

and the billing type determining unit is used for determining the type of the target account to be settled according to the account to be settled.

The account processing device based on the account accessor provided by the embodiment of the invention can execute the account processing method based on the account accessor provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Example IV

Fig. 4 shows a schematic diagram of an electronic device 400 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 4, the electronic device 400 includes at least one processor 410, and a memory, such as a Read Only Memory (ROM) 420, a Random Access Memory (RAM) 430, etc., communicatively coupled to the at least one processor 410, wherein the memory stores computer programs executable by the at least one processor, and the processor 410 may perform various suitable actions and processes according to the computer programs stored in the Read Only Memory (ROM) 420 or the computer programs loaded from the storage unit 480 into the Random Access Memory (RAM) 430. In (RAM) 430, various programs and data required for the operation of electronic device 400 may also be stored. The processors 410, (RAM) 420, and (RAM) 430 are connected to each other by a bus 440. An input/output (I/O) interface 450 is also connected to bus 440.

Various components in electronic device 400 are connected to I/O interface 450, including: an input unit 460 such as a keyboard, a mouse, etc.; an output unit 470 such as various types of displays, speakers, and the like; a storage unit 480 such as a magnetic disk, an optical disk, or the like; and a communication unit 490, such as a network card, modem, wireless communication transceiver, etc. The communication unit 490 allows the electronic device 400 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks.

Processor 410 can be a variety of general-purpose and/or special-purpose processing components having processing and computing capabilities. Some examples of processor 410 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 410 performs the various methods and processes described above, such as an account accessor-based accounting method.

In some embodiments, an account accessor-based accounting method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 480. In some embodiments, part or all of the computer program may be loaded and/or installed onto electronic device 400 via (RAM) 420 and/or communication unit 490. When the computer program is loaded into (RAM) 430 and executed by processor 410, one or more steps of an account accessor-based accounting method described above may be performed. Alternatively, in other embodiments, processor 410 may be configured to perform an account accessor-based accounting method in any other suitable manner (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. An account processing method based on an account accessor, which is characterized by comprising the following steps:

2. The method of claim 1, wherein obtaining a first account accessor to be used from the target billing scenario comprises:

3. The method of claim 1, wherein combining the first account accessor and the second account accessor to access a target account to be settled to invoke a public operation of a target account type and invoke a personalized operation of the target account type in a target billing scenario to obtain a billing processing result comprises:

4. The method of claim 1, wherein the target account object corresponding to the target account type comprises a base operation interface and a public operation interface to be invoked; the basic operation interface comprises at least one of the following: a checkout interface, a payment interface, an expiration date interface, or an entry of input data; and the public operation interface is an operation interface for dynamically binding and calling the account accessor for the target account type.

5. The method of claim 1, wherein the second account accessor comprises a common account accessor for encapsulating the operation of each account type in common in each billing scenario.

6. The method of claim 1, wherein determining, via the unified billing center interface, the target billing scenario in which to reside and the target account type to be settled in response to the billing request of the service module comprises:

determining a billing mode, an account to be settled and a transaction link in response to a billing request of a service module through a unified billing center interface;

Selecting a target billing scene from the candidate billing scenes according to the billing mode and the transaction link;

and determining the type of the target account to be settled according to the account to be settled.

7. An account accessor-based accounting processing device, comprising:

8. The apparatus of claim 7, wherein the first accessor acquisition module is specifically configured to:

9. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement an account accessor-based accounting method as claimed in any one of claims 1-6.

10. A computer readable storage medium having stored thereon a computer program which when executed by a processor implements an account accessor-based accounting method as claimed in any one of claims 1-6.