CN112581257A - Dispute service management method, system, device and medium supporting different card organizations - Google Patents
Dispute service management method, system, device and medium supporting different card organizations Download PDFInfo
- Publication number
- CN112581257A CN112581257A CN202011483769.5A CN202011483769A CN112581257A CN 112581257 A CN112581257 A CN 112581257A CN 202011483769 A CN202011483769 A CN 202011483769A CN 112581257 A CN112581257 A CN 112581257A
- Authority
- CN
- China
- Prior art keywords
- dispute
- service
- login user
- processing
- target
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 60
- 238000012545 processing Methods 0.000 claims abstract description 122
- 230000008520 organization Effects 0.000 claims abstract description 44
- 238000000034 method Methods 0.000 claims abstract description 43
- 230000008569 process Effects 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 6
- 230000001960 triggered effect Effects 0.000 claims description 5
- 238000006243 chemical reaction Methods 0.000 claims description 4
- 238000005538 encapsulation Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 abstract description 7
- 230000006870 function Effects 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 3
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- BQCADISMDOOEFD-UHFFFAOYSA-N Silver Chemical compound [Ag] BQCADISMDOOEFD-UHFFFAOYSA-N 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 229910052709 silver Inorganic materials 0.000 description 1
- 239000004332 silver Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Abstract
The invention discloses a dispute service management method, system, device and medium supporting different card organizations, the method comprises: inquiring the role authority of the login user according to the information of the login user; the role right item at least comprises target card organization information to which the login user belongs; generating a dispute service processing menu according to the role authority of the login user; and if the fact that the login user triggers the target service in the dispute service processing menu is detected, processing the target service according to the target card organization information and the target service information based on the dispute service processing official letter. The technical scheme of the embodiment of the invention controls the access and the operation authority of the login user to the dispute service resource based on the role access control technology, effectively maintains the confidentiality and the security of dispute service processing, improves the dispute service processing efficiency and realizes fine management.
Description
Technical Field
The embodiment of the invention relates to a plug-in technology and a role access control technology, in particular to a dispute service management method, a dispute service management system, dispute service management equipment and a dispute service management medium which support different card organizations.
Background
With the development of society and science and technology, bank business interconnection and intercommunication, the number of cards to be processed is increased, and the dispute business process involved in each transaction is more and more complex, so that higher requirements are made on the processing capacity and efficiency of bank dispute business.
At present, the conventional error dispute management system develops exclusive process management based on different card organizations, and dispute processes of different card organizations (such as VISA, MasterCard, chinese union pay and JCB) are different, so that a set of process management scheme needs to be designed for dispute error processes of each card organization.
The traditional error dispute management system is complex in design, inflexible in service logic and poor in system module sharing. When the business logic of a card organization changes, the card can be redeveloped according to the new business logic only, and the modification workload is large.
Disclosure of Invention
The invention provides a dispute service management method, a dispute service management system, a dispute service management device and a dispute service management medium which support different card organizations, so that the dispute service processing efficiency is improved, and the fine management is realized.
In a first aspect, an embodiment of the present invention provides a method for managing dispute services supporting different card organizations, where the method includes:
inquiring the role authority of the login user according to the information of the login user; the role right item at least comprises target card organization information to which the login user belongs;
generating a dispute service processing menu according to the role authority of the login user;
and if the fact that the login user triggers the target service in the dispute service processing menu is detected, processing the target service according to the target card organization information and the target service information based on the dispute service processing official letter.
In a second aspect, an embodiment of the present invention further provides a dispute service management system supporting different card organizations, where the dispute service management system includes:
the system display module is used for generating and displaying a dispute service processing menu according to the role authority of the login user;
the role authority management module is used for user role management and user authority parameter configuration;
the plug-in and resource management module is used for plug-in interface configuration, plug-in parameter configuration and resource and authority management;
the business flow module is used for encapsulating dispute business processing logic into a notarization and reserving an adjustable interface;
the data access module is used for connecting a database through a data access interface to realize data access, conversion and encapsulation;
and the information resource module is used for storing dispute service processing data and logs.
In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the dispute service management method of any embodiment of the present invention.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the dispute service management method according to any embodiment of the present invention.
According to the dispute service management method, system, device and medium supporting different card organizations provided by the embodiment of the invention, most of service flows and processing logics are encapsulated into a public letter, the access and operation permission of login users to dispute service resources are controlled based on a role access control technology, different card organizations can only operate and access allowed information, the confidentiality and the safety of dispute service processing are effectively maintained, the operation processing efficiency of dispute rear ends is improved, and fine management is realized.
Drawings
FIG. 1 is a flow chart of dispute service management supporting different card organizations according to an embodiment of the present invention;
FIG. 2 is a flow chart of dispute service management supporting different card organizations according to a second embodiment of the present invention;
FIG. 3 is a flow chart of dispute service management supporting different card organizations according to a third embodiment of the present invention;
FIG. 4 is a block diagram of a dispute service management system supporting different card organizations according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of a dispute service management process supporting different card organizations according to an embodiment of the present invention, which is applicable to a situation that a dispute service process is more and more complicated as the number of card types increases. The method can be executed by dispute service management systems supporting different card organizations, and can be applied to electronic equipment.
The method specifically comprises the following steps:
s110, inquiring the role authority of the login user according to the information of the login user; the role right item at least comprises target card organization information of the login user.
Card organization, known as bank card transfer clearing institution (also called credit card organization/bank card organization). Currently, International card organizations include the wits International organization (VISA International), the MasterCard International organization (MasterCard International), american Express, and the union of silver International corporation. The card organization is responsible for constructing and operating a global or regional uniform payment card information exchange network, is responsible for information conversion and fund clearing of payment card transactions, and establishes and enforces payment card cross-bank transaction service specifications and technical standards. The dispute service processing flows of different card organizations are different.
The rights can be understood as operations on the functional module in the application system. Deletion of uploaded files, access to menus, and even visibility control of a certain button and a certain picture on a page can belong to the scope of authority. A role is understood to be a collection of a certain number of rights, which is the carrier of rights. For example: in a forum system, "super manager" and "host" are roles; the edition owner may manage posts within the edition, may manage users within the edition, and the like, which are rights. If a certain user is to be granted these rights, the rights do not need to be directly granted to the user, and the role of "copyright owner" can be given to the user.
In this embodiment, the login user is a service operator of the card organization, which may be a service operator, or a service reviewer. The information of the login user is pre-stored in a database and comprises the following steps: at least one of an operator name, a post number, a card organization to which it belongs, a post level, a post category, and a role privilege.
The dispute service processing flows of different card organizations are different, the service types mainly responsible for the service personnel at different service posts and post levels when processing the dispute service are different, different role authorities can be configured for different service personnel in the database according to the card organizations, posts or post levels of the service personnel, and the confidentiality and the security of dispute service processing are effectively maintained.
In this embodiment, when the user logs in, the role authority corresponding to the login user may be queried according to the information of the login user pre-stored in the database. The role authority can include access authority and operation authority of disputed business resources.
And S120, generating a dispute service processing menu according to the role authority of the login user.
The dispute service processing menu only displays dispute service resources which can be accessed or operated by the login user. In this embodiment, the dispute service processing menu is generated based on the role authority of the login user, so that the access and operation authority of the role of the login user to the dispute service resource (for example, a plug-in and a system function point) can be effectively controlled, different cards organize the information that the login user at different posts can only operate and access the authorization, thereby effectively maintaining the confidentiality of the dispute service management system, and improving the security and the service compliance of the system.
S130, if the fact that the login user triggers the target service in the dispute service processing menu is detected, processing the target service according to the target card organization information and the target service information based on the dispute service processing official letter.
The dispute service trigger may have various forms, for example, a dispute service processing menu may be clicked to operate, or a target service to be processed may be input by voice, which is not limited in this embodiment.
In this embodiment, based on the enterprise-level process optimization methodology and the operation control standard, the credit card dispute service process is optimized, different card organization acceptance standards are integrated, and dispute acceptance standardization is achieved. After the error dispute process of the card organization is standardized, the dispute service process and the processing logic of the card organization can be encapsulated into a notarization, and different roles and position parameters are configured according to the requirements of the affiliated responsibility service department, so that the dispute service management system can be used for processing the dispute service process.
Illustratively, the dispute service processing letter is formed by extracting a simplified dispute service processing flow and encapsulating processing operations for realizing the related flow. The processing flow of the target service A comprises the following steps: see case-request-refuse payment-request again-arbitration. If the target service A is triggered, the target service and the target card organization information are transmitted, and when the official letter is called, the calling of a plurality of interface plug-ins of 'watching case, asking for money, refusing to pay again, asking for money again and arbitrating' can be realized, so that the target service A is finished.
According to the technical scheme of the embodiment, most of service flows and processing logics are encapsulated into a letter, access and operation permission of login users to dispute service resources are controlled based on a role access control technology, different cards organize login users at different posts and only allowed information of operation and access, confidentiality and safety of dispute service processing are effectively maintained, operation processing efficiency of dispute rear ends is improved, and fine management is achieved.
Example two
Fig. 2 is a flowchart of dispute service management supporting different card organizations according to a second embodiment of the present invention, which is further optimized based on the second embodiment of the present invention, and a detailed description is given of how to query the role authority of the login user according to the information of the login user.
Specifically, as shown in fig. 2, the method includes the following steps:
s210, checking whether the identity of the login user is legal or not according to the information of the login user.
The information of the login user is pre-stored in a database, and comprises the following steps: at least one of an operator name, a post number, a card organization to which it belongs, a post level, a post category, and a role privilege.
In this embodiment, verifying whether the identity of the login user is legal may be understood as querying whether the login user exists in the database, and if not, the login user is not a legal login user, and does not have a right to perform dispute service processing; and if so, acquiring the information of the login user from the database so as to judge the information in the following.
And S220, if the user is legal, judging whether the role authority is configured for the user or not according to the information of the login user. If not, executing S230; otherwise, S240 is performed.
Since the information of the login user is pre-stored in the database, the method comprises the following steps: at least one of an operator name, a post number, a card organization to which it belongs, a post level, a post category, and a role privilege. As can be seen, there may be situations where no role privileges are configured for a logged-in user in the database.
In this embodiment, whether role authority has been configured for the user is determined according to the information of the login user. If the role authority is configured for the login user in the database, inquiring the role authority of the login user; and if the role authority is not configured for the login user in the database, configuring the role authority for the login user.
And S230, configuring role authority for the login user.
Because dispute service processing flows of different card organizations are different, and the types of services mainly responsible for login users of different service posts and post levels when processing dispute services are different, different role authorities can be configured for different login users in the database according to the card organizations, posts or post levels of the login users.
And S240, inquiring the role authority of the login user.
And S250, generating a dispute service processing menu according to the role authority of the login user.
Wherein, the authority comprises the access authority and the operation authority of the service resource. The dispute service processing menu comprises: at least one of card organization information, case single number, card number, processing amount, current state, and next node state. The dispute service processing process comprises at least one functional node, such as a request, a refusal payment and arbitration.
In this embodiment, the service resources within the authority range of the login user are determined according to the role authority of the login user, and a dispute service processing menu is generated according to the service resources within the authority range of the login user.
Optionally, generating a dispute service processing menu according to the role authority of the login user may include: determining service resources with access rights according to the role rights of the login user; and generating an accessible dispute service processing menu according to the service resources with the access authority.
Optionally, generating a dispute service processing menu according to the role authority of the login user, which may further include: determining service resources with operation authority according to the role authority of the login user; and generating an operable dispute service processing menu according to the service resources with the operation authority.
Illustratively, if the login user 1 is a rechecker in the card organization V, the login user has access to the service resources A, C, D and E, and has operation right to the service resource B; login user 2 is an operator in card organization C, and has operating rights to business resources A, C and E, and access rights to business resource B. The dispute service processing menu generated when the user 1 logs in is different from the dispute service processing menu generated when the user 2 logs in.
And S260, if the fact that the login user triggers the target service in the dispute service processing menu is detected, processing the target service according to the target card organization information and the target service information on the basis of the dispute service processing official letter.
According to the technical scheme of the embodiment, before inquiring the role authority of the login user, whether the identity of the login user is legal or not is judged, the login user without the dispute service processing authority is preliminarily filtered, then the role authority is configured for the login user without the role authority according to the affiliated card organization, post or post level of the login user, the service resources in the authority range of the login user are determined according to the inquired role authority of the login user, the dispute service processing menu is generated according to the service resources in the authority range of the login user, the dispute service processing menu can be simplified, and the dispute service processing efficiency is improved.
EXAMPLE III
Fig. 3 is a flowchart of dispute service management supporting different card organizations according to a third embodiment of the present invention, and the method is further optimized based on the third embodiment, and a specific description is given of how to process a target service based on a public function. As shown in fig. 3, the method includes:
s310, inquiring the role authority of the login user according to the information of the login user; the role right item at least comprises target card organization information of the login user.
And S320, generating a dispute service processing menu according to the role authority of the login user.
S330, if the target service in the dispute service processing menu triggered by the login user is detected, generating a target service request message according to the target card organization information and the target service information.
The dispute service trigger may have various forms, for example, a dispute service processing menu may be clicked to operate, or a target service to be processed may be input by voice, which is not limited in this embodiment. And if the target service in the dispute service processing menu is detected to be triggered, generating a corresponding target service request message according to the triggered target service information and the target card organization information. In this embodiment, the target service request packet is used to invoke a target service related operation. The target service may be a denial of service, an arbitration, or other common dispute service processing methods, and the embodiment is not limited in this embodiment.
S340, analyzing the target service request message, processing the target service according to the target card organization information and the target service information based on the dispute service processing official letter.
The dispute service processing letter is packaged with processing logic of different dispute services in different card organizations. At least one outbound message is embedded in the service processing official letter and used for finishing at least one operation of dispute service processing, such as payment request, refund, receipt and the like.
In this embodiment, the target service and the target card organization information can be obtained by analyzing the target service request message. And calling outbound plug-ins of other interfaces through outbound messages to process the target service based on the dispute service processing letter according to the target card organization information and the target service information. And after the outbound plug-in completes the processing of the corresponding target service function node, returning an outbound message result. And updating the memory database of the dispute service system according to the returned outbound message result. If the target service needs to call a plurality of outbound plug-ins to complete the processing of the target service, after the calling of the outbound plug-ins is finished, whether the next operation is continued or not is judged according to the outbound return result. If so, calling the next outbound plug-in to process the target service, and updating the database according to the returned outbound message result until the whole dispute service processing flow is completed. And storing the processing record and the log of the target service, and displaying the processing result of the target service on an interface.
Illustratively, if the calling message calls the money request operation, the returned calling message result contains the success of the money request or the refusal of the money request, and then whether the next operation is performed is judged according to the money request result.
Optionally, the service processing official letter may include at least one dispute service processing sub-official letter, where a dispute service processing logic is encapsulated in the sub-official letter, and an outbound message corresponding to the dispute service is embedded in the sub-official letter. It can be understood that the flow of performing the dispute service processing includes at least one functional node, and the sub-official document may be understood as that, corresponding to one functional node performing the dispute service processing, the dispute service processing logic of one functional node is encapsulated, and an outbound message of the corresponding functional node is embedded to complete the service processing operation of the one functional node.
And if at least one dispute service logic of the card organization is changed, updating the service logic and the outbound message of the card organization in the corresponding at least one dispute service processing letter. After the update is completed, dispute service processing can be performed based on the updated dispute service processing letter.
According to the technical scheme of the embodiment, dispute service flows and processing logics organized by the card are encapsulated into a letter, and outbound messages of different other interfaces are assembled to complete service operation of different functional nodes, so that the coupling between dispute services is reduced, the functional nodes can be independently developed, mutual dependency does not exist, and independent functions can be independently operated, so that the flexibility of the whole flow is improved. For modifying the processing flow of a certain dispute service, the normal operation of other dispute services can not be influenced, the development difficulty is reduced, the development efficiency is improved, and the expandability of the dispute service processing flow is improved.
Example four
Fig. 4 is a structural block diagram of a dispute service management system supporting different card organizations according to a fourth embodiment of the present invention, which is used for executing the dispute service management method supporting different card organizations according to the fourth embodiment of the present invention, so that confidentiality and security of dispute service processing can be effectively maintained, operation processing efficiency at a dispute back end is improved, and fine management is implemented. As shown in fig. 4, the system includes a module system exhibition module 410, a role authority management module 420, a plug-in and resource management module 430, a business process module 440, a data access module 450, and an information resource module 460.
The system display module 410 is configured to generate and display a dispute service processing menu according to the role authority of the login user;
a role authority management module 420 for user role management and user authority parameter configuration;
the plug-in and resource management module 430 is used for plug-in interface configuration, plug-in parameter configuration and resource and authority management;
the business process module 440 is used for encapsulating dispute business processing logic into a notarization and reserving an adjustable interface;
the data access module 450 is used for connecting a database through a data access interface to realize data access, conversion and encapsulation;
and the information resource module 460 is used for storing dispute service processing data and logs.
The dispute service management system supporting different card organizations provided by the fourth embodiment of the present invention can execute the dispute service management method supporting different card organizations provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method. Most of business processes and processing logics are encapsulated into a notarization, access and operation permission of login users to dispute business resources are controlled based on a role access control technology, different cards organize login users at different posts and only allowed information of operation and access, confidentiality and safety of dispute business processing are effectively maintained, operation processing efficiency of dispute rear ends is improved, and fine management is achieved.
EXAMPLE five
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. FIG. 5 illustrates a block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 5 is only an example and should not bring any limitation to the function and the scope of use of the embodiment of the present invention.
As shown in FIG. 5, electronic device 12 is embodied in the form of a general purpose computing device. The components of electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 5, and commonly referred to as a "hard drive"). Although not shown in FIG. 5, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
The processing unit 16 executes programs stored in the system memory 28 to perform various functional applications and data processing, such as implementing the dispute service management method supporting different card organizations provided by the embodiment of the present invention.
EXAMPLE six
A sixth embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a dispute service management method supporting different card organizations according to any embodiment of the present invention.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. 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 (a non-exhaustive list) of the computer readable storage medium would include the following: 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 context of this document, 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.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, 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 wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like 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).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (15)
1. A dispute service management method supporting different card organizations, the method comprising:
inquiring the role authority of the login user according to the information of the login user; the role right item at least comprises target card organization information to which the login user belongs;
generating a dispute service processing menu according to the role authority of the login user;
and if the fact that the login user triggers the target service in the dispute service processing menu is detected, processing the target service according to the target card organization information and the target service information based on the dispute service processing official letter.
2. The method of claim 1, wherein generating a dispute service handling menu according to the role authority of the login user comprises:
determining service resources with access rights according to the role rights of the login user;
and generating an accessible dispute service processing menu according to the service resources with the access authority.
3. The method of claim 1, wherein generating a dispute service handling menu according to the role authority of the login user comprises:
determining service resources with operation authority according to the role authority of the login user;
and generating an operable dispute service processing menu according to the service resources with the operation authority.
4. The method of claim 1, wherein the information of the logged-on user is stored in a database, comprising:
at least one of an operator name, a post number, a card organization to which it belongs, a post level, a post category, and a role privilege.
5. The method of claim 1, wherein querying the role authority of the login user according to the information of the login user comprises:
checking whether the identity of the login user is legal or not according to the information of the login user;
and if the login user is legal, inquiring the role authority of the login user.
6. The method of claim 5, further comprising, before querying the role authority of the logged-in user:
judging whether role authority is configured for the user or not according to the information of the login user;
and if not, configuring role authority for the login user.
7. The method of claim 1, wherein if it is detected that the login user triggers a target service in a dispute service handling menu, processing the target service according to the target card organization information and the target service information based on a dispute service handling official letter, comprising:
if the target service in the dispute service processing menu triggered by the login user is detected, generating a target service request message according to the target card organization information and the target service information;
and analyzing the target service request message, and processing the target service according to the target card organization information and the target service information based on a dispute service processing official letter.
8. The method of claim 7 wherein said dispute service handling letter has encapsulated therein processing logic for different dispute services in different card organizations.
9. The method of claim 8 wherein at least one outbound message is embedded in said dispute service handling letter for performing at least one operation of dispute service handling.
10. The method of claim 7 wherein said dispute service handling notations include at least one dispute service handling sub-notations, said sub-notations encapsulating a dispute service handling logic and embedding an outbound message corresponding to said dispute service.
11. The method according to claim 9 or 10, wherein processing the target service according to the target card organization information and the target service information based on a dispute service processing official letter comprises:
calling at least one outbound plug-in to process the target service;
and updating a memory database of the dispute service system according to the returned outbound message result, storing the processing record and the log of the target service, and displaying the processing result of the target service on an interface.
12. The method according to claim 9 or 10, comprising:
if at least one dispute service logic of the card organization changes, updating the service logic and the outbound message of the card organization in the corresponding at least one dispute service processing letter;
and performing dispute service processing based on the updated dispute service processing official letter.
13. A dispute traffic management system supporting different card organizations, the system comprising:
the system display module is used for generating and displaying a dispute service processing menu according to the role authority of the login user;
the role authority management module is used for user role management and user authority parameter configuration;
the plug-in and resource management module is used for plug-in interface configuration, plug-in parameter configuration and resource and authority management;
the business flow module is used for encapsulating dispute business processing logic into a notarization and reserving an adjustable interface;
the data access module is used for connecting a database through a data access interface to realize data access, conversion and encapsulation;
and the information resource module is used for storing dispute service processing data and logs.
14. An electronic device, characterized in that the electronic device comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a dispute traffic management method as recited in any of claims 1-12.
15. A computer-readable storage medium having stored thereon a computer program, wherein the program, when executed by a processor, implements a dispute traffic management method as claimed in any one of claims 1 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011483769.5A CN112581257A (en) | 2020-12-15 | 2020-12-15 | Dispute service management method, system, device and medium supporting different card organizations |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011483769.5A CN112581257A (en) | 2020-12-15 | 2020-12-15 | Dispute service management method, system, device and medium supporting different card organizations |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112581257A true CN112581257A (en) | 2021-03-30 |
Family
ID=75135321
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011483769.5A Pending CN112581257A (en) | 2020-12-15 | 2020-12-15 | Dispute service management method, system, device and medium supporting different card organizations |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112581257A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113095806A (en) * | 2021-04-09 | 2021-07-09 | 中国工商银行股份有限公司 | Work order processing method and device, electronic equipment and computer readable storage medium |
| CN113806724A (en) * | 2021-09-29 | 2021-12-17 | 杭州迪普科技股份有限公司 | Method and device for processing user login request |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1352777A (en) * | 1999-05-11 | 2002-06-05 | 科利肯赛特·达康公司 | System and method for providing complete non-judical dispute resolution management and operation |
| CN104221045A (en) * | 2011-12-30 | 2014-12-17 | 环联有限责任公司 | System and method for automated dispute resolution of credit data |
| CN110378789A (en) * | 2019-07-16 | 2019-10-25 | 招商银行股份有限公司 | Solution, system and the computer readable storage medium of disputed transaction |
| CN110458555A (en) * | 2019-06-28 | 2019-11-15 | 平安银行股份有限公司 | Dispute process method, apparatus, electronic equipment and storage medium |
| CN111144873A (en) * | 2019-12-31 | 2020-05-12 | 交通银行股份有限公司北京市分行 | Electronic purchase order based bill receiving mechanism bill receiving dispute processing method and system |
| CN111429155A (en) * | 2020-03-25 | 2020-07-17 | 中国银行股份有限公司 | Bank card dispute processing method and device |
-
2020
- 2020-12-15 CN CN202011483769.5A patent/CN112581257A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1352777A (en) * | 1999-05-11 | 2002-06-05 | 科利肯赛特·达康公司 | System and method for providing complete non-judical dispute resolution management and operation |
| CN104221045A (en) * | 2011-12-30 | 2014-12-17 | 环联有限责任公司 | System and method for automated dispute resolution of credit data |
| CN110458555A (en) * | 2019-06-28 | 2019-11-15 | 平安银行股份有限公司 | Dispute process method, apparatus, electronic equipment and storage medium |
| CN110378789A (en) * | 2019-07-16 | 2019-10-25 | 招商银行股份有限公司 | Solution, system and the computer readable storage medium of disputed transaction |
| CN111144873A (en) * | 2019-12-31 | 2020-05-12 | 交通银行股份有限公司北京市分行 | Electronic purchase order based bill receiving mechanism bill receiving dispute processing method and system |
| CN111429155A (en) * | 2020-03-25 | 2020-07-17 | 中国银行股份有限公司 | Bank card dispute processing method and device |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113095806A (en) * | 2021-04-09 | 2021-07-09 | 中国工商银行股份有限公司 | Work order processing method and device, electronic equipment and computer readable storage medium |
| CN113095806B (en) * | 2021-04-09 | 2024-01-30 | 中国工商银行股份有限公司 | Work order processing method and device, electronic equipment and computer readable storage medium |
| CN113806724A (en) * | 2021-09-29 | 2021-12-17 | 杭州迪普科技股份有限公司 | Method and device for processing user login request |
| CN113806724B (en) * | 2021-09-29 | 2024-02-09 | 杭州迪普科技股份有限公司 | User login request processing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110310205B (en) | Block chain data monitoring method, device, equipment and medium | |
| TWI576719B (en) | Secure service for receiving sensitive information through nested iframes | |
| CN108764901B (en) | Leasing method, system, equipment and storage medium based on block chain technology | |
| CN110032599B (en) | Data structure reading and updating method and device, and electronic equipment | |
| US10614454B1 (en) | Remote population and redaction of high security data | |
| KR20060043629A (en) | Project time and expense | |
| US9037537B2 (en) | Automatic redaction of content for alternate reviewers in document workflow solutions | |
| US10474843B2 (en) | Identifying stolen databases | |
| WO2021244474A1 (en) | Login data processing method, apparatus, device and system | |
| JP2012533824A (en) | Systems and methods for real-time batch account processing | |
| US20130013507A1 (en) | System to Create and Manage Payment Accounts | |
| CN110138767B (en) | Transaction request processing method, device, equipment and storage medium | |
| US20200294124A1 (en) | Blockchain-based method, apparatus, and device | |
| CN113254969B (en) | Business data processing method and device, electronic equipment and storage medium | |
| CN112581257A (en) | Dispute service management method, system, device and medium supporting different card organizations | |
| CN113761552A (en) | Access control method, device, system, server and storage medium | |
| CN110070360B (en) | Transaction request processing method, device, equipment and storage medium | |
| CN113612766A (en) | Data management device, method, computer equipment and storage medium | |
| CN110827142A (en) | User credit evaluation method, system, server and storage medium | |
| CN113282890A (en) | Resource authorization method, device, electronic equipment and storage medium | |
| CN115114670B (en) | File unlocking method and device based on external link, network disk and storage medium | |
| CN112801772B (en) | Trusted method, trusted processing system, electronic equipment and storage medium | |
| US20230119117A1 (en) | Security for connected devices | |
| CN113821277A (en) | Interface calling method and device, computer readable storage medium and electronic equipment | |
| CN115904351A (en) | Service logic implementation method, device, equipment and storage medium based on JSSDK |
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 |