CN114331418A - Method for monitoring agent based on payment mode and related device - Google Patents
Method for monitoring agent based on payment mode and related device Download PDFInfo
- Publication number
- CN114331418A CN114331418A CN202111614868.7A CN202111614868A CN114331418A CN 114331418 A CN114331418 A CN 114331418A CN 202111614868 A CN202111614868 A CN 202111614868A CN 114331418 A CN114331418 A CN 114331418A
- Authority
- CN
- China
- Prior art keywords
- payment
- agent
- payment mode
- rule base
- rule
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention provides a method for monitoring an agent based on a payment mode and a related device, wherein the method comprises the following steps: obtaining a ticket drawing request of an agent; judging whether the payment mode and the agent identification are matched with a preset payment mode rule base or not according to the payment mode and the agent identification in the ticket issuing request of the agent; if the payment mode and the agent identification are matched with a preset payment mode rule base, allowing the ticket drawing; if the payment mode and the agent identification are not matched with the preset payment mode rule base, the ticket drawing is not allowed; the payment method can be checked when the agent issues the ticket according to the requirements of the international aviation association and the airline company, and the ticket issuing is refused when the payment method does not meet the requirements, so that different agents can be managed differently.
Description
Technical Field
The invention belongs to the technical field of civil aviation trip information, and particularly relates to a method and a related device for monitoring an agent based on a payment mode.
Background
At present, each airline company checks each agent only to check whether the password is correct, for example, when each agent sends a ticket issuing request to the corresponding airline company, the corresponding airline company checks the password of the request, and when the check is completed, the ticket issuing is allowed; when the verification fails, the ticket drawing is not allowed. The ticket selling qualification of corresponding flights can be verified.
However, in the prior art, the payment modes of the agents cannot be distinguished and limited, and the payment modes allowed to be used by each agent are consistent; resulting in inconvenience of differentiated management.
Disclosure of Invention
In view of the above, the present invention provides a method and a related device for monitoring an agent based on a payment method, which are used for monitoring according to the payment method of the agent to achieve differentiated management of different agents.
The application discloses in a first aspect a method for monitoring an agent based on a payment mode, comprising:
obtaining a ticket drawing request of an agent;
judging whether the payment mode and the agent identification are matched with a preset payment mode rule base or not according to the payment mode and the agent identification in the ticket drawing request of the agent;
if the payment mode and the agent identification are matched with a preset payment mode rule base, allowing ticket drawing;
and if the payment mode and the agent identification are not matched with a preset payment mode rule base, not allowing the ticket drawing.
Optionally, the setting process of the payment method rule base includes:
and reading in the set rules in batches, storing the rules into a database, and taking the database as the payment mode rule base.
Optionally, the batch reading of the set rules and the storage of the set rules in a database, and taking the database as the payment method rule base, includes:
and the international aviation association standard file is read in an interface through a standard file, and the rule corresponding to the international aviation association standard file is transmitted to the payment mode rule base.
Optionally, the setting process of the payment method rule base includes:
and (4) adopting a single entry mode, entering the manually input rules into a database, and taking the database as the payment mode rule base.
Optionally, a separate entry mode is adopted, the manually input rule is entered into a database, and the database is used as the payment mode rule base, including:
acquiring a rule instruction; the rule instruction is an instruction for manually inputting corresponding rule information;
generating a corresponding rule according to the rule instruction;
and storing the rules into the payment mode rule base.
Optionally, the payment rules corresponding to the business departments in the payment method rule base are independent of each other.
Optionally, before or after any step, the method may further include:
and inquiring the rules in the payment mode rule base.
The second aspect of the present application discloses a device for monitoring an agent based on a payment method, including:
the acquisition module is used for acquiring a ticket issuing request of an agent;
the matching module is used for judging whether the payment mode and the agent identification are matched with a preset payment mode rule base or not according to the payment mode and the agent identification in the ticket issuing request of the agent;
the ticket issuing module is used for allowing ticket issuing if the payment mode and the agent identifier are matched with a preset payment mode rule base; and if the payment mode and the agent identification are not matched with a preset payment mode rule base, not allowing the ticket drawing.
A third aspect of the present application discloses an electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement a method for monitoring agents based on a payment method as described in any one of the first aspects of the present application.
A fourth aspect of the present application discloses a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a method for monitoring an agent based on a payment method according to any one of the first aspect of the present application.
According to the technical scheme, the method for monitoring the agent based on the payment mode comprises the following steps: obtaining a ticket drawing request of an agent; judging whether the payment mode and the agent identification are matched with a preset payment mode rule base or not according to the payment mode and the agent identification in the ticket issuing request of the agent; if the payment mode and the agent identification are matched with a preset payment mode rule base, allowing the ticket drawing; if the payment mode and the agent identification are not matched with the preset payment mode rule base, the ticket drawing is not allowed; the payment method can be checked when the agent issues the ticket according to the requirements of the international aviation association and the airline company, and the ticket issuing is refused when the payment method does not meet the requirements, so that different agents can be managed differently.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart of a method for monitoring an agent based on a payment method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for monitoring an agent for filewise loading rules based on payment according to an embodiment of the present invention;
FIG. 3 is a flowchart of manual rule input in a method for monitoring an agent based on a payment method according to an embodiment of the present invention;
fig. 4 is a flowchart of rule application in a method for monitoring an agent based on a payment method according to an embodiment of the present invention;
fig. 5 is a schematic diagram of an apparatus for monitoring an agent based on a payment method according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of another device for monitoring agents based on payment methods according to an embodiment of the present invention;
fig. 7 is a schematic diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, 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". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The embodiment of the application provides a method for monitoring agents based on payment modes, which is used for solving the problem that the payment modes of the agents cannot be distinguished and limited in the prior art, and the payment modes allowed to be used by each agent are consistent; resulting in a problem of inconvenient distinction management.
Referring to fig. 1, the method for monitoring an agent based on a payment method includes:
s101, obtaining a ticket drawing request of the agent.
Wherein the ticketing request includes: payment means and agent identification. Of course, other information may also be included, which is not described in detail herein, and all of which are within the protection scope of the present application depending on the actual situation.
S102, judging whether the payment mode and the agent identification are matched with a preset payment mode rule base or not according to the payment mode and the agent identification in the ticket drawing request of the agent.
It should be noted that, in order to enhance the management of the ticket-drawing fund of the monitoring agent and prevent the fund risk, the international aviation association pushes a series of documents, so as to hopefully reduce the deposit lag payment.
Meanwhile, in order to strengthen the monitoring and the restriction of the payment mode of the airline company to the business department, the agent and the like.
It should be noted that the payment method rule base includes each agent identifier and the corresponding payment method. Of course, the system may also include a business department identifier and a payment method rule thereof, which are not described herein again one by one and are all within the protection scope of the present application.
The payment methods to be controlled may include Cash (CA, Cash), Credit Card (CC, Credit Card), and the payment methods to be supported may include international aeronautical association easy pay (EP, easy), which is not described herein again.
If the payment method and the agent identifier match with the preset payment method rule base, step S103 is executed.
S103, allowing the ticket drawing.
If the payment method and the agent identifier do not match the preset payment method rule base, step S104 is executed.
And S104, not allowing the ticket drawing.
It should be noted that step S102, step S103, and step S104 may be as shown in fig. 4; specifically, rule checking is carried out during ticket drawing; judging whether the rule meets the limit, and checking whether the rule passes the ticket or not when the rule meets the limit; when the limit is not met, the ticket drawing is not allowed. Of course, the present invention is not limited thereto, and the details are not repeated herein and are within the scope of the present application.
In the embodiment, a ticket drawing request of an agent is obtained; judging whether the payment mode and the agent identification are matched with a preset payment mode rule base or not according to the payment mode and the agent identification in the ticket issuing request of the agent; if the payment mode and the agent identification are matched with a preset payment mode rule base, allowing the ticket drawing; if the payment mode and the agent identification are not matched with the preset payment mode rule base, the ticket drawing is not allowed; that is, according to the requirements of the international aviation association and the airline company, when the agent issues the ticket, the payment mode of the agent is checked, and if the payment mode does not meet the requirement, the agent refuses to issue the ticket, so that the agent is convenient to distinguish and manage.
In practical applications, there may be multiple setting processes of the payment method rule base, and the following two cases are described respectively:
(1) and reading in the set rules in batches, storing the rules into a database, and taking the database as a payment mode rule base.
Specifically, the process of reading in the set rules in batch and storing the rules in the database, and taking the database as the payment mode rule base may be:
as shown in fig. 2, the FOP standard file of the international aviation association is read in through the standard file read-in interface, and the rule corresponding to the FOP standard file of the international aviation association is transmitted to the payment method rule base.
It should be noted that the operation of batch reading may be executed at a fixed time or when a preset condition is met, and is not described herein any more, and is within the scope of the present application depending on the actual situation.
(2) And (4) adopting a single entry mode, entering the manually input rules into a database, and taking the database as a payment mode rule base.
Specifically, as shown in fig. 3, a separate entry mode is adopted, the manually input rule is entered into the database, and the process of using the database as the payment mode rule base may be:
acquiring a rule instruction; the rule instruction is an instruction for manually inputting corresponding rule information. The rule information may include the identity of each agent and its corresponding payment method. Of course, the system may also include a business department identifier and a payment method rule thereof, which are not described herein again one by one and are all within the protection scope of the present application.
And generating a corresponding rule according to the rule instruction.
And storing the rules into a payment mode rule base.
The modes in (1) and (2) may be applied simultaneously or only one of them, and are not specifically limited herein, and are within the scope of the present application as appropriate.
In practical applications, the expected granularity of control in the payment method rule base is the business department.
The payment rules corresponding to the business departments are mutually independent.
The business department may be an airline company, and the payment rules of each airline company are independent of each other.
When the payment rules corresponding to the business departments are independent, the ticket drawing request carries the business department identification. Since the agent needs to submit the corresponding request through the corresponding business department, the ticket drawing request of the agent automatically contains the corresponding business department identifier.
It should be noted that the control granularity includes BSP ticket region, that is, the rule for each agent is different; meanwhile, the granularity control department is added; that is, the rules for different airlines are different, that is, the configured airline company prohibits the agent from using a certain payment method, and does not affect other airlines to allow the agent to use a certain payment method.
Wherein, the BSP ticket refers to the ticket issued by the agent.
It should be noted that the flow of the above steps S101 to S105 is to determine whether the ticket can be issued according to the payment method, that is, whether the payment method of the corresponding agent is limited.
Based on the flow, the application also discloses a query flow; that is to say, the agent can automatically inquire the payment mode allowed to be used by the agent; specifically, the query process may be parallel to the above process, and therefore, the query process may be executed before or after any step of the above process.
Therefore, as shown in fig. 4, before and after any step, the method may further include:
and inquiring the rules in the payment mode rule base.
It should be noted that the query is mainly for querying the payment method that the agent is allowed to use, so that the agent knows the payment method that the agent can use.
Specifically, a query request of an agent is obtained; then, according to the inquiry request, rule inquiry is carried out to obtain a corresponding payment mode, and the agent is informed of the payment mode allowed to be used.
It should be noted that, when the payment rules corresponding to the business departments are independent from each other, the query request may carry a business department identifier. Since the agent needs to submit the corresponding request through the corresponding business department, the inquiry request of the agent automatically contains the corresponding business department identifier.
In the embodiment, the international aviation association standard file can be automatically and regularly analyzed, the payment mode of the agent can be controlled by the airline company in real time, whether the agent can use the payment mode can be inquired, and the payment mode of the agent can be checked when the agent draws a ticket according to the requirements of the international aviation association and the airline company, and the ticket drawing is rejected and related prompts are given when the agent does not conform to the requirements of the international aviation association and the airline company.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the 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 the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
Another embodiment of the invention provides a device for monitoring an agent based on a payment mode.
Referring to fig. 5, the device for monitoring the agent based on the payment method includes:
and the obtaining module 10 is used for obtaining the ticket issuing request of the agent.
And the matching module 20 is used for judging whether the payment mode and the agent identifier are matched with a preset payment mode rule base or not according to the payment mode and the agent identifier in the ticket issuing request of the agent.
The ticket issuing module 30 is configured to allow ticket issuing if the payment method and the agent identifier are matched with a preset payment method rule base; and if the payment mode and the agent identification are not matched with a preset payment mode rule base, not allowing the ticket drawing.
For details of the working process and principle of each module, reference is made to the method for monitoring the agent based on the payment method provided by the above embodiment, which is not described herein any more, and all are within the protection scope of the present application.
Specifically, as shown in fig. 6, the agent monitoring apparatus based on the payment method is described as follows:
(1) and (5) reading in the module in batches.
Because the current configuration has a flow of a part of control rules recorded by an international aviation association mail, the module can be extended to the current mode, the function of the module is developed and completed by running configuration, and the host part provides a standard interface for the output data of the configuration department to call.
The interface is designed as a black screen instruction of a seat ordering system, and the format is as follows: DDI, office name/payment method/Y (yes) orN (no); for example: DDI PEK 123/FPCC/Y; of course, the present invention is not limited thereto, and details are not described herein any more, and all that is required is within the scope of the present application, depending on the actual situation.
The function of the batch read-in module is as follows: and the DDI displays a new option of the ticket issuing authorization instruction, responds to the call required to be carried out during configuration input, and writes the data into a rule base.
The input of the batch read-in module is as follows: and the DDI displays the ticket issuing authorization instruction and the instruction content.
The output of the batch read-in module is as follows: the rule data is passed to a rule base.
The related procedures of the batch read-in module are as follows: and paying the mode management program after drawing the ticket.
(2) And (5) logging the modules individually.
The independent entry module is used for independently controlling whether an agent can use a certain payment mode to carry out configuration according to the needs of an airline user. The instructions are consistent with the interface provided to the configuration; of course, more detailed parameters for specifically adapting to the airline, as well as identity, level control, etc. may also be added.
It should be noted that the identity refers to the role of an airline worker, such as an administrator or a general employee; and, levels, such as 9, 11, 33, etc., the lower the number the higher the level.
The function of the single recording module is as follows: and the DDI displays a new option of the ticket issuing authorization instruction, responds to the call required to be carried out during configuration input, and writes the data into a rule base.
The inputs to the individual entry module are: and the DDI displays the ticket issuing authorization instruction and the instruction content.
The output of this separate logging module is: the rule data is passed to a rule base.
The relevant programs of the individual logging modules: and paying the mode management program after drawing the ticket.
(3) And a rule storage module.
The rule storage module is a rule base, the granularity is the level of business departments, namely, each business department has corresponding rule control. Referring to the existing environment of the system, the rule base borrows the payment mode identification, and an identification group is newly established in the payment mode to identify whether the business department or the agent can use a certain payment mode.
The function of the rule storage module is as follows: and storing the rules.
The inputs of the rule storage module are: and newly building DDI to display the data flow of the ticket drawing authorization instruction.
The output of the rule storage module is: rule inquiry request and ticket checking request.
The related procedures of the rule storage module are as follows: and identifying a payment mode.
(4) And a rule application module.
The rule application module can call related rule data in the rule storage, display the rule, check whether business departments and agents meet related limits in the actual ticket drawing process, and interrupt the ticket drawing request and give a prompt if the business departments and the agents do not meet the related limits.
The rule application module has the functions of: and (5) rule display and rule check.
The rule application module has the following inputs: a user query request and a user ticket drawing request.
The output of the rule application module is: the query feedback is displayed in a DDI (data center interface) for displaying the ticket drawing authorization display.
The ticketing feedback is presented to the user at a prompt, such as a limit: the IATA international airline prohibits the payment method, and the like, and is not specifically limited herein, and is within the protection scope of the present application as long as the international airline is determined according to actual conditions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may 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 the like.
Another embodiment of the present application provides a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a method for monitoring an agent based on a payment method as in any one of the above embodiments.
In the context of this disclosure, a machine-readable medium may 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. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable 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. 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.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or 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 electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having 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. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
Another embodiment of the present invention provides an electronic device, as shown in fig. 7, including:
one or more processors 601.
A storage device 602 having one or more programs stored thereon.
The one or more programs, when executed by the one or more processors 601, cause the one or more processors 601 to implement a method for payment-based agent monitoring as any one of the embodiments described above.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
While several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Claims (10)
1. A method for monitoring an agent based on a payment mode is characterized by comprising the following steps:
obtaining a ticket drawing request of an agent;
judging whether the payment mode and the agent identification are matched with a preset payment mode rule base or not according to the payment mode and the agent identification in the ticket drawing request of the agent;
if the payment mode and the agent identification are matched with a preset payment mode rule base, allowing ticket drawing;
and if the payment mode and the agent identification are not matched with a preset payment mode rule base, not allowing the ticket drawing.
2. The method for monitoring the agent based on the payment method as claimed in claim 1, wherein the setting process of the payment method rule base comprises:
and reading in the set rules in batches, storing the rules into a database, and taking the database as the payment mode rule base.
3. The method for monitoring agents based on payment methods of claim 2, wherein the batch reading in the set rules and storing into a database, the database being the payment method rule base, comprises:
and the international aviation association standard file is read in an interface through a standard file, and the rule corresponding to the international aviation association standard file is transmitted to the payment mode rule base.
4. The method for monitoring the agent based on the payment method as claimed in claim 1, wherein the setting process of the payment method rule base comprises:
and (4) adopting a single entry mode, entering the manually input rules into a database, and taking the database as the payment mode rule base.
5. The method of monitoring agents based on payment methods of claim 4, wherein the manual rules are entered into a database as the payment method rule base in a separate entry manner, comprising:
acquiring a rule instruction; the rule instruction is an instruction for manually inputting corresponding rule information;
generating a corresponding rule according to the rule instruction;
and storing the rules into the payment mode rule base.
6. The method of claim 1, wherein the payment rules associated with each business department in the payment rules repository are independent of each other.
7. The method for monitoring agents based on payment method as claimed in any one of claims 1-6, further comprising before or after any step:
and inquiring the rules in the payment mode rule base.
8. An agent monitoring device based on payment mode, comprising:
the acquisition module is used for acquiring a ticket issuing request of an agent;
the matching module is used for judging whether the payment mode and the agent identification are matched with a preset payment mode rule base or not according to the payment mode and the agent identification in the ticket issuing request of the agent;
the ticket issuing module is used for allowing ticket issuing if the payment mode and the agent identifier are matched with a preset payment mode rule base; and if the payment mode and the agent identification are not matched with a preset payment mode rule base, not allowing the ticket drawing.
9. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method for monitoring agents based on payment methods of any one of claims 1-6.
10. A computer storage medium, having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a method for monitoring agents based on a payment method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111614868.7A CN114331418A (en) | 2021-12-27 | 2021-12-27 | Method for monitoring agent based on payment mode and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111614868.7A CN114331418A (en) | 2021-12-27 | 2021-12-27 | Method for monitoring agent based on payment mode and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114331418A true CN114331418A (en) | 2022-04-12 |
Family
ID=81012365
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111614868.7A Pending CN114331418A (en) | 2021-12-27 | 2021-12-27 | Method for monitoring agent based on payment mode and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114331418A (en) |
-
2021
- 2021-12-27 CN CN202111614868.7A patent/CN114331418A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9747598B2 (en) | Dynamic security code push | |
| WO2019100308A1 (en) | Business trip reimbursement method, system, storage medium and terminal | |
| US20130304637A1 (en) | Fraud control integrated form filling tool | |
| US11816669B2 (en) | Index of usability for a replacement payment card | |
| US11122049B2 (en) | Attribute database system and method | |
| CN111222973B (en) | Information processing system and method | |
| US10803459B2 (en) | Online transaction processing system for multi-product transactions | |
| US20240078535A1 (en) | Digital wallet management system | |
| AU2014377626A1 (en) | Method and system for virtual account number-based travel expense controls and accounting | |
| US12008577B2 (en) | System and method for facilitating reclamation requests | |
| EP3651106A1 (en) | Systems and methods for generating a digital identity of equipment on an equipment online marketplace platform | |
| CN110972500B (en) | System and method for payment management | |
| CN114331418A (en) | Method for monitoring agent based on payment mode and related device | |
| US10303335B2 (en) | Multicomputer processing of client device request data with centralized event orchestration | |
| CN114265876A (en) | Blacklist passenger checking interception method, related device and computer storage medium | |
| US11494832B2 (en) | Systems and methods for securely creating a listing of equipment on an equipment online marketplace platform | |
| US20170278019A1 (en) | Online transaction processing system for multi-product transactions | |
| KR20190101868A (en) | System for managing expense and method using therewith | |
| EP4163843A1 (en) | Payment consolidation for a travel management system | |
| KR102612583B1 (en) | System and method for representing licenses for export and computer program for the same | |
| US20170278158A1 (en) | Online transaction processing system for multi-product transactions | |
| US20170278163A1 (en) | Online transaction processing system for multi-product transactions | |
| US20220374894A1 (en) | Integrated payment travel management system | |
| CN117217942A (en) | Cross-system data interaction method, device and storage medium | |
| CN114297707A (en) | Electronic ticket information protection method, related device and computer storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |