Agent Monitoring Method and Related Devices Based on Payment Methods

Abstract

The present invention provides a method and related device for monitoring an agent based on a payment method. The method includes: obtaining a ticket issuing request of the agent; determining whether the payment method and the agent identifier in the ticket issuing request of the agent match a pre-set payment method rule base; if the payment method and the agent identifier match the pre-set payment method rule base, allowing ticket issuing; if the payment method and the agent identifier do not match the pre-set payment method rule base, not allowing ticket issuing; that is, it is possible to check the payment method of the agent when the agent issues a ticket according to the requirements of the International Air Transport Association and airlines, and reject ticket issuing when it does not meet the requirements, which is convenient for differentiating management of different agents.

Description

Technical Field

[0001] The present invention belongs to the technical field of civil aviation travel information technology. More specifically, it particularly relates to a method and related device for monitoring agents based on payment methods. Background Art

[0002] Currently, when each airline verifies each agent, generally only the correctness of its password is verified. For example, when each agent sends a ticket issuing request to the corresponding airline, the corresponding airline verifies the password of the request. When the verification is completed, ticket issuing is allowed; when the verification fails, ticket issuing is not allowed. It is also possible to verify whether the agent has the qualification to sell tickets for the corresponding flight.

[0003] However, in the prior art, it is impossible to distinguish and restrict the payment methods of agents, and each agent is allowed to use the same payment methods; this makes it inconvenient to distinguish and manage. Summary of the Invention

[0004] In view of this, an object of the present invention is to provide a method and related device for monitoring agents based on payment methods, which are used to monitor according to the payment methods of agents and achieve differential management of different agents.

[0005] The first aspect of this application discloses a method for monitoring agents based on payment methods, including:

[0006] Obtain the ticket issuing request of the agent;

[0007] According to the payment method and agent identifier in the ticket issuing request of the agent, determine whether the payment method and the agent identifier match the pre-set payment method rule library;

[0008] If the payment method and the agent identifier match the pre-set payment method rule library, allow ticket issuing;

[0009] If the payment method and the agent identifier do not match the pre-set payment method rule library, do not allow ticket issuing.

[0010] Optionally, the setting process of the payment method rule library includes:

[0011] Batch read the set rules and store them in the database, and use the database as the payment method rule library.

[0012] Optionally, the batch reading of the set rules and storing them in the database, and using the database as the payment method rule library includes:

[0013] The rules corresponding to the International Air Transport Association standard file are transmitted to the payment method rule library through the standard file reading interface of the International Air Transport Association standard file.

[0014] Optionally, the setting process of the payment method rule library includes:

[0015] Adopt the method of separate entry to enter the manually input rules into the database, and use the database as the payment method rule library.

[0016] Optionally, adopting the method of separate entry to enter the manually input rules into the database and using the database as the payment method rule library includes:

[0017] Obtain a rule instruction; wherein, the rule instruction is an instruction for manually inputting corresponding rule information.

[0018] Generate corresponding rules according to the rule instruction.

[0019] Store the rules in the payment method rule library.

[0020] Optionally, the payment rules corresponding to each business department in the payment method rule library are independent of each other.

[0021] Optionally, before and after any step, it may further include:

[0022] Query the rules in the payment method rule library.

[0023] The second aspect of the present application discloses a monitoring device for agents based on payment methods, including:

[0024] An acquisition module, configured to acquire a ticket issuing request of an agent.

[0025] A matching module, configured to determine whether the payment method and the agent identifier in the ticket issuing request of the agent match a pre-set payment method rule library.

[0026] A ticket issuing module, configured to allow ticket issuing if the payment method and the agent identifier match a pre-set payment method rule library; and not allow ticket issuing if the payment method and the agent identifier do not match a pre-set payment method rule library.

[0027] The third aspect of the present application discloses an electronic device, characterized by including:

[0028] One or more processors;

[0029] A storage device, on which one or more programs are stored;

[0030] When the one or more programs are executed by the one or more processors, the one or more processors implement the monitoring method for agents based on payment methods as described in any item of the first aspect of the present application.

[0031] The fourth aspect of the present application discloses a computer storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the method for monitoring an agent based on a payment method as described in any one of the first aspects of the present application.

[0032] As can be seen from the above technical solutions, a method for monitoring an agent based on a payment method provided by the present invention includes: obtaining a ticket issuing request of the agent; judging whether the payment method and the agent identifier in the ticket issuing request of the agent match a pre-set payment method rule base; if the payment method and the agent identifier match the pre-set payment method rule base, allowing ticket issuing; if the payment method and the agent identifier do not match the pre-set payment method rule base, not allowing ticket issuing; that is, it is possible to check the payment method of the agent when the agent issues a ticket according to the requirements of the International Air Transport Association and airlines, and reject ticket issuing when it does not meet the requirements, which is convenient for differentiating management of different agents. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0034] Figure 1 is a flowchart of a method for monitoring an agent based on a payment method provided by an embodiment of the present invention;

[0035] Figure 2 is a flowchart of a file loading rule in a method for monitoring an agent based on a payment method provided by an embodiment of the present invention;

[0036] Figure 3 is a flowchart of manual rule input in a method for monitoring an agent based on a payment method provided by an embodiment of the present invention;

[0037] Figure 4 is a flowchart of rule application in a method for monitoring an agent based on a payment method provided by an embodiment of the present invention;

[0038] Figure 5 is a schematic diagram of a device for monitoring an agent based on a payment method provided by an embodiment of the present invention;

[0039] Figure 6 is a schematic diagram of another device for monitoring an agent based on a payment method provided by an embodiment of the present invention;

[0040] Figure 7It is a schematic diagram of an electronic device provided by an embodiment of the present invention. Detailed implementation manners

[0041] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0042] The term "including" and its variations used herein are open-ended, that is, "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0043] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0044] It should be noted that the modification of "one" and "multiple" mentioned in the present disclosure is illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly stated in the context, it should be understood as "one or more".

[0045] An embodiment of the present application provides a method for monitoring an agent based on a payment method, which is used to solve the problem in the prior art that it is impossible to distinguish and restrict the payment methods of agents, and the payment methods allowed for each agent are the same, resulting in inconvenient differential management.

[0046] See Figure 1 , the method for monitoring an agent based on a payment method includes:

[0047] S101. Obtain the ticket issuing request of the agent.

[0048] Wherein, the ticket issuing request includes: a payment method and an agent identifier. Of course, it may also include other information, which will not be elaborated here one by one and can be determined according to the actual situation, and all are within the protection scope of the present application.

[0049] S102. Determine whether the payment method and the agent identifier in the ticket issuing request of the agent match the pre-set payment method rule library.

[0050] It should be noted that in order to strengthen the management of the funds for issuing tickets by monitoring agents and prevent fund risks, the International Air Transport Association has introduced a series of documents in the hope of reducing the occurrence of overdue payment of deposits.

[0051] At the same time, to strengthen the monitoring and restraint of the payment methods of airlines for business departments, agents, etc.

[0052] It should be noted that in this payment method rule library, it includes various agent identifiers and their corresponding payment methods. Of course, it may also include business department identifiers and their payment method rules, etc., which will not be elaborated one by one here and are all within the protection scope of this application.

[0053] The payment methods that are expected to be controlled may include cash (CA, Cash), credit card (CC, Credit Card), and the payment methods that will be supported in the future may include the International Air Transport Association EasyPay (EP, Easypay), etc. which will not be elaborated one by one here and can be determined according to the actual situation, and are all within the protection scope of this application.

[0054] If the payment method and the agent identifier match the pre-set payment method rule library, then step S103 is executed.

[0055] S103: Allow ticket issuance.

[0056] If the payment method and the agent identifier do not match the pre-set payment method rule library, then step S104 is executed.

[0057] S104: Do not allow ticket issuance.

[0058] It should be noted that step S102, step S103, and step S104 can be as Figure 4 shown; specifically, the rule check is carried out when issuing a ticket; it is judged whether the rule meets the restrictions. When it meets the restrictions, the check passes and ticket issuance is allowed; when it does not meet the restrictions, ticket issuance is not allowed. Of course, it is not limited to this, which will not be elaborated one by one here and are all within the protection scope of this application.

[0059] In this embodiment, the ticket issuance request of the agent is obtained; according to the payment method and the agent identifier in the ticket issuance request of the agent, it is judged whether the payment method and the agent identifier match the pre-set payment method rule library; if the payment method and the agent identifier match the pre-set payment method rule library, then ticket issuance is allowed; if the payment method and the agent identifier do not match the pre-set payment method rule library, then ticket issuance is not allowed; that is, it can, according to the requirements of the International Air Transport Association and the airline, check the payment method of the agent when the agent issues a ticket, and if it does not meet the requirements, ticket issuance should be refused, which is convenient for differential management.

[0060] In practical applications, there are various ways to set up the above payment method rule library. The following explains two cases separately:

[0061] (1) Batch read the set rules and store them in the database, and use the database as the payment method rule library.

[0062] Specifically, the process of batch reading the set rules and storing them in the database and using the database as the payment method rule library can be as follows:

[0063] As Figure 2 shown, through the standard file reading interface of the International Air Transport Association (IATA) FOP standard file, the rules corresponding to the IATA standard file are transmitted to the payment method rule library.

[0064] It should be noted that this batch reading operation can be executed regularly or when a preset condition is met. Details are not elaborated here and can be determined according to the actual situation, all within the scope of protection of this application.

[0065] (2) Adopt the method of separate entry, enter the manually input rules into the database, and use the database as the payment method rule library.

[0066] Specifically, as Figure 3 shown, the process of adopting the method of separate entry, entering the manually input rules into the database, and using the database as the payment method rule library can be:

[0067] Obtain a rule instruction; among them, the rule instruction is an instruction for manually inputting corresponding rule information. The rule information may include various agent identifiers and their corresponding payment methods. Of course, it may also include the business department identifier and its payment method rules, etc. Details are not elaborated here and are all within the scope of protection of this application.

[0068] Generate corresponding rules according to the rule instruction.

[0069] Store the rules in the payment method rule library.

[0070] It should be noted that the methods in (1) and (2) can be applied simultaneously or only one of them can be applied. Specific limitations are not made here and can be determined according to the actual situation, all within the scope of protection of this application.

[0071] In practical applications, the expected control granularity in the payment method rule library is the business department.

[0072] The payment rules corresponding to each business department are independent of each other.

[0073] Among them, the business department can be an airline company, that is, the payment rules of each airline company are independent of each other.

[0074] When the payment rules corresponding to each business department are independent, the ticket issuing request carries the business department identifier. Since the agent needs to submit corresponding requests through the corresponding business department, the ticket issuing request will automatically include the corresponding business department identifier.

[0075] It should be noted that the control granularity includes the BSP ticket region, that is, the rules for each agent are different; at the same time, the control granularity is also increased to the business department; that is, the rules for different airlines are different. That is, configuring an airline to prohibit an agent from using a certain payment method does not affect other airlines allowing the agent to use a certain payment method.

[0076] Among them, the BSP ticket refers to the ticket issued by the agent.

[0077] It should be noted that the above process of steps S101 - S105 is to determine whether a ticket can be issued based on the payment method, that is, whether the payment method of the corresponding agent is restricted.

[0078] Based on the above process, this application also discloses a query process; that is, the agent can independently query the payment methods allowed for itself; specifically, the query process can be parallel to the above process. Therefore, the query process can be executed before or after any step of the above process.

[0079] Therefore, as Figure 4 shown, before or after any step, it may also include:

[0080] Query the rules in the payment method rule library.

[0081] It should be noted that this query is mainly to query the payment methods allowed for the agent so that the agent can understand the payment methods available to itself.

[0082] Specifically, obtain the query request of the agent; then, based on the query request, perform a rule query to obtain the corresponding payment method and notify the agent of the payment methods allowed for it.

[0083] It should be noted that when the payment rules corresponding to each business department are independent, the query request can carry the business department identifier. Since the agent needs to submit corresponding requests through the corresponding business department, the query request will automatically include the corresponding business department identifier.

[0084] In this embodiment, it can automatically and regularly parse the International Air Transport Association standard file, can accept real-time control of the agent's payment method by the airline, the payment methods that the agent can use can be queried, and, according to the requirements of the International Air Transport Association and the airline, when the agent issues a ticket, check its payment method, and if it does not meet the requirements, reject the ticket and give relevant prompts.

[0085] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are for illustrative purposes only and are not used to limit the scope of these messages or information.

[0086] Although the operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous.

[0087] It should be understood that the various steps recited in the method embodiments of the present disclosure may be executed in a different order and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.

[0088] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or combinations thereof. The foregoing programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0089] Another embodiment of the present invention provides an agent monitoring device based on a payment method.

[0090] See Figure 5 , the agent monitoring device based on the payment method includes:

[0091] An acquisition module 10, configured to acquire a ticket issuing request of an agent.

[0092] A matching module 20, configured to determine whether the payment method and the agent identifier in the ticket issuing request of the agent match a pre-set payment method rule library.

[0093] A ticket issuing module 30, configured to allow ticket issuing if the payment method and the agent identifier match a pre-set payment method rule library; and not allow ticket issuing if the payment method and the agent identifier do not match a pre-set payment method rule library.

[0094] For the working processes and principles of the above-mentioned modules, for details, refer to the method for monitoring agents based on payment methods provided in the above-mentioned embodiments. Details will not be elaborated here one by one, and all are within the protection scope of this application.

[0095] Specifically, as Figure 6 shown, an example is used to illustrate the device for monitoring agents based on payment methods as follows:

[0096] (1) Batch reading module.

[0097] Since there is already a process of inputting some control rules through emails of the International Air Transport Association in the current configuration, this module can continue to use the current method. The function of this module is developed by operation configuration. The host part provides a standard interface for the configuration section to output data for calling.

[0098] The interface is designed as a black screen instruction for the seat reservation system, and the format is: DDI: office name / payment method / Y (yes) or N (no); for example: DDI: PEK123 / FPCC / Y; of course, it is not limited to this. Details will not be elaborated here one by one, and it depends on the actual situation, and all are within the protection scope of this application.

[0099] The function of this batch reading module is: The DDI display ticket issuance authorization instruction adds an option option, responds to the call required when the configuration is input, and writes the data into the rule library.

[0100] The input of this batch reading module is: The DDI display ticket issuance authorization instruction and the instruction content.

[0101] The output of this batch reading module is: Rule data to the rule library.

[0102] The related program of this batch reading module is: The payment method management program after ticket issuance.

[0103] (2) Individual input module.

[0104] The individual input module is for airline users to configure whether agents can use a certain payment method according to their own needs. The instruction is consistent with the interface provided for configuration; of course, more detailed parameters such as those specifically adapted to airlines, as well as identity and level control, etc. can also be added.

[0105] It should be noted that this identity refers to the roles of airline staff, such as administrators and ordinary employees; and the level, such as 9, 11, 33, etc. The smaller the number, the higher the level.

[0106] The function of this individual input module is: The DDI display ticket issuance authorization instruction adds an option option, responds to the call required when the configuration is input, and writes the data into the rule library.

[0107] The input of this separate entry module is: the DDI display ticket authorization instruction and the instruction content.

[0108] The output of this separate entry module is: rule data to the rule library.

[0109] The related program of this separate entry module is: the payment method management program after ticket issuance.

[0110] (3) Rule storage module.

[0111] The rule storage module is the rule library, with the granularity at the business department level, that is, each business department has corresponding rule control. Referring to the existing environment of the system, the rule library will borrow the payment method identifier and create a new identifier group in the payment method to identify whether a certain business department or agent can use a certain payment method.

[0112] The function of this rule storage module is: rule storage.

[0113] The input of this rule storage module is: the newly created DDI display ticket authorization instruction data stream.

[0114] The output of this rule storage module is: rule query request, ticket issuance check request.

[0115] The related program of this rule storage module is: payment method identifier.

[0116] (4) Rule application module.

[0117] The rule application module can call the relevant rule data in the rule storage, display the rules, and during the actual ticket issuance process, check whether the business department and the agent meet the relevant restrictions. If not, the ticket issuance request will be interrupted and a prompt will be given.

[0118] The functions of this rule application module are: rule display, rule check.

[0119] The inputs of this rule application module are: user query request, user ticket issuance request.

[0120] The output of this rule application module is: the query feedback is displayed on the DDI display ticket authorization display.

[0121] The ticket issuance feedback is displayed as a prompt to the user. If there are restrictions, for example, it is prompted that: This payment method is prohibited for IATA international routes, etc. No specific limitations are set here, and it depends on the actual situation, all within the protection scope of this application.

[0122] The units involved in the embodiments of the present disclosure can be implemented in software or in hardware. Among them, the name of the unit does not constitute a limitation on the unit itself in some cases. For example, the first acquisition unit can also be described as "the unit for acquiring at least two Internet protocol addresses".

[0123] The functions described above herein can be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), and so on.

[0124] Another embodiment of the present application provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the agent monitoring method based on the payment method as described in any one of the above embodiments.

[0125] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer disk, 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.

[0126] It should be noted that the above computer-readable medium in the present disclosure may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present disclosure, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium, and this computer-readable signal medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted by any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0127] The above computer-readable medium may be included in the above electronic device; or it may exist separately without being assembled into the electronic device.

[0128] Another embodiment of the present invention provides an electronic device, as Figure 7 shown, including:

[0129] One or more processors 601.

[0130] A storage device 602, on which one or more programs are stored.

[0131] When one or more programs are executed by one or more processors 601, the one or more processors 601 are caused to implement the agent monitoring method based on the payment method as described in any one of the above embodiments.

[0132] In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, an embodiment of the present disclosure includes a computer program product that includes a computer program carried on a non-transitory computer-readable medium, the computer program including program code for performing the methods shown in the flowcharts.

[0133] Although the subject matter has been described in language specific to structural features and / or methodological acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. On the contrary, the specific features and acts described above are merely example forms for implementing the claims.

[0134] Although a number of specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment can also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0135] The above description is only a preferred embodiment of the present disclosure and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of the disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosure concept. For example, the technical solutions formed by mutually replacing the above features with the technical features (but not limited to) having similar functions disclosed in the present disclosure.

Claims

1. A method for monitoring an agent based on a payment method, characterized in that, Including: Obtaining the ticket issuing request of the agent; Based on the business department identifier, payment method, and agency identifier in the ticket issuing request of the agent, determining whether the payment method and the agency identifier match the payment method rules corresponding to the business department identifier in the pre-set payment method rule library, so as to determine whether the agent can make a payment through the payment method; the payment method rule library includes each business department identifier and its payment method rules; If the payment method and the agency identifier match the payment method rules corresponding to the business department identifier in the pre-set payment method rule library, ticket issuing is allowed; If the payment method and the agency identifier do not match the payment method rules corresponding to the business department identifier in the pre-set payment method rule library, ticket issuing is not allowed.

2. The method for monitoring an agent based on a payment method according to claim 1, characterized in that, The setting process of the payment method rule library includes: Batch reading the set rules and storing them in the database, and using the database as the payment method rule library.

3. The method for monitoring an agent based on a payment method according to claim 2, characterized in that, The batch reading the set rules and storing them in the database, and using the database as the payment method rule library includes: The International Air Transport Association standard file is read through the standard file reading interface, and the rules corresponding to the International Air Transport Association standard file are transmitted to the payment method rule library.

4. The method for monitoring an agent based on a payment method according to claim 1, characterized in that, The setting process of the payment method rule library includes: In a separate entry manner, manually input rules are entered into the database, and the database is used as the payment method rule library.

5. The method for monitoring an agent based on a payment method according to claim 4, characterized in that, In a separate entry manner, manually input rules are entered into the database, and the database is used as the payment method rule library includes: Obtaining a rule instruction; wherein, the rule instruction is an instruction for manually inputting corresponding rule information; Generating corresponding rules according to the rule instruction; Storing the rules into the payment method rule library.

6. The method for monitoring an agent based on a payment method according to claim 1, characterized in that, The payment rules corresponding to each business department in the payment method rule library are independent of each other.

7. The method for monitoring an agent based on a payment method according to any one of claims 1-6, characterized in that, Before and after any step, it may further include: Querying the rules in the payment method rule library.

8. An apparatus for monitoring an agent based on a payment method, characterized in that, Including: An obtaining module, configured to obtain the ticket issuing request of the agent; A matching module, configured to determine whether the payment method and the agency identifier match the payment method rules corresponding to the business department identifier in the pre-set payment method rule library based on the business department identifier, payment method, and agency identifier in the ticket issuing request of the agent, so as to determine whether the agent can make a payment through the payment method; the payment method rule library includes each business department identifier and its payment method rules; A ticket issuing module, configured to allow ticket issuing if the payment method and the agency identifier match the payment method rules corresponding to the business department identifier in the pre-set payment method rule library; and not allow ticket issuing if the payment method and the agency identifier do not match the payment method rules corresponding to the business department identifier in the pre-set payment method rule library.

9. An electronic device, characterized in that, Including: One or more processors; A storage device, on which one or more programs are stored; When one or more programs are executed by one or more processors, the one or more processors implement the method for monitoring an agent based on a payment method as described in any one of claims 1-6.

10. A computer storage medium, characterized in that, A computer program is stored thereon, wherein when the computer program is executed by a processor, the method for monitoring an agent based on a payment method as described in any one of claims 1-6 is implemented.

Images