CN108376364B - Payment system account checking method and device and terminal device - Google Patents
Payment system account checking method and device and terminal device Download PDFInfo
- Publication number
- CN108376364B CN108376364B CN201810124678.9A CN201810124678A CN108376364B CN 108376364 B CN108376364 B CN 108376364B CN 201810124678 A CN201810124678 A CN 201810124678A CN 108376364 B CN108376364 B CN 108376364B
- Authority
- CN
- China
- Prior art keywords
- information
- service
- data table
- reconciliation
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/35—Clustering; Classification
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Software Systems (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention belongs to the technical field of electronic information, and provides a payment system account checking method, equipment and terminal equipment, wherein the payment system account checking method comprises the following steps: classifying the service messages to obtain different types of service messages; constructing a corresponding data table according to different types of service messages; storing the service message of each category into a corresponding data table, and storing service information into a preset message classification attribute table, wherein the service information comprises information in the data table; after receiving an account checking notification sent by a center end of a payment system, receiving and storing account checking information sent by the center end, and performing account checking according to the account checking information and the message classification attribute table. The invention improves the account checking expansibility of the payment system, reduces the expansion cost and has stronger usability and practicability.
Description
Technical Field
The invention belongs to the technical field of electronic information, and particularly relates to a payment system account checking method, payment system account checking equipment and terminal equipment.
Background
In the current payment system, with the development of society, some new transaction modes and transaction scenarios appear, for example: code scanning payment, cardless payment, etc. The new increase of transaction scenes causes some new business requirements to appear in commercial banks. And the central end of the payment channel system can upgrade the original system in order to support the new service requirements. The manner of upgrading is typically to add new service messaging scenarios to support these emerging service needs.
However, these new services involve the transfer of funds and require financial checks. In the traditional payment system, the business bank end checks accounts one by one according to the existing business message and the data sent by the center end. When a new service message is added to the system, the transaction record of the newly added service message cannot be checked in the original mode, the system expansibility is poor, and the expansion cost is high.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method, a device, and a terminal device for checking account of a payment system, so as to improve the expandability of the checking account of the payment system and reduce the expansion cost.
A first aspect of an embodiment of the present invention provides a method for reconciliation of a payment system, including:
classifying the service messages to obtain different types of service messages;
constructing a corresponding data table according to different types of service messages;
storing the service message of each category into a corresponding data table, and storing service information into a preset message classification attribute table, wherein the service information comprises information in the data table;
after receiving an account checking notification sent by a center end of a payment system, receiving and storing account checking information sent by the center end, and performing account checking according to the account checking information and the message classification attribute table.
A second aspect of an embodiment of the present invention provides a device for reconciliation of a payment system, including:
the classification module is used for classifying the service messages to obtain different types of service messages;
the processing module is used for constructing a corresponding data table according to the different types of service messages;
the storage module is used for storing the service message of each category into a corresponding data table and storing the service information into a preset message classification attribute table, wherein the service information comprises information in the data table;
and the reconciliation module is used for receiving and storing reconciliation information sent by the central end after receiving a reconciliation notice sent by the central end of the payment system, and performing reconciliation according to the reconciliation information and the message classification attribute table.
A third aspect of the embodiments of the present invention provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method when executing the computer program.
A fourth aspect of embodiments of the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method as described above.
Compared with the prior art, the embodiment of the invention has the following beneficial effects: in the embodiment of the invention, the service messages are classified to obtain different types of service messages; constructing a corresponding data table according to different types of service messages; storing the service message of each category into a corresponding data table, and storing service information into a preset message classification attribute table, wherein the service information comprises information in the data table; after receiving an account checking notification sent by a center end of a payment system, receiving and storing account checking information sent by the center end, and performing account checking according to the account checking information and the message classification attribute table. The embodiment of the invention improves the account checking expansibility of the payment system and reduces the expansion cost by classifying the services, thereby having stronger usability and practicability.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic flow chart of an implementation of a method for reconciliation of a payment system according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of an implementation of a method for reconciling by a payment system according to a second embodiment of the present invention;
fig. 3 is a schematic diagram of a device for reconciling payment systems provided by the third embodiment of the invention;
fig. 4 is a schematic diagram of a terminal device according to a fourth embodiment of the present invention.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In order to explain the technical means of the present invention, the following description will be given by way of specific examples.
Fig. 1 is a schematic flow chart of an implementation of a method for reconciliation of a payment system according to an embodiment of the present invention, where the method shown in fig. 1 may include the following steps:
step S101, classifying the service messages to obtain different types of service messages.
In the embodiment of the invention, the payment system is composed of an intermediary institution providing payment clearing service and professional technical means for realizing payment instruction transmission and fund clearing, and is used for realizing financial arrangement of debt and debt clearing and fund transfer. The payment system may be, for example, a system that provides a clearing of funds for payment transactions between commercial banks or between a commercial bank and a central bank. The payment system may include a payment system central side, which may be used by a central bank, and a payment system commercial bank side, which may be used by a commercial bank. Optionally, the embodiment of the invention can be used for a commercial bank end of a payment system.
In the embodiment of the invention, the service message comprises service data information. For example, in the embodiment of the present invention, the service messages may be classified by comparing information such as message elements, service attributes, service properties, and processing flows of different service messages, for example, service messages with message element similarity higher than a preset value (e.g., 80%) and/or processing flow similarity higher than a preset value and/or with the same service properties (e.g., as a payment-type service) may be classified into one class.
And step S102, constructing a corresponding data table according to the different types of service messages.
For example, in the embodiment of the present invention, based on the same point or similarity of information such as a message element, a service attribute, a service property, and a processing flow of a service message of the same category, a corresponding data table may be constructed according to contents such as an account checking element field of the service message, for example, for a payment service, the account checking element field may include: message serial number, service type serial number, incoming and outgoing account mark, service state, loan mark and amount; the information service includes: message number, message serial number and service state. The data tables storing the service messages of the same category can have high similarity or the same table structure by extracting the same or high similarity elements of the service messages of the same category and constructing the corresponding data tables.
Optionally, in the embodiment of the present invention, if a new service packet is received, determining a category of the new service packet, determining whether the category exists in an existing category, and if so, storing the new service packet in a data table corresponding to the category; if not, judging whether the existing data tables have the data tables meeting the preset conditions or not, if so, revising the data tables meeting the preset conditions according to preset rules, storing the new service message into the revised data tables, and updating the category information and the data table information; if the existing data table does not have a data table meeting the preset conditions, a corresponding new data table is created according to the category of the new service message, the new service message is stored in the new data table, and category information and data table information are updated.
For example, in the data table meeting the preset condition in the embodiment of the present invention, the similarity between the reconciliation element field, the service attribute, and other elements of the newly added service packet and the elements included in the existing data table is higher than a preset value, and if the similarity is higher than 80%, the newly added service packet may be classified into the category corresponding to the data table, the category corresponding to the data table may be modified according to the newly added service packet, the elements included in the data table may be clustered according to the elements of the newly added service packet, and the category information and the data table information may be updated, so that the reconciliation on the newly added service may be implemented in the subsequent reconciliation according to the updated category information and the data table information without re-determining and updating the information.
In the embodiment of the invention, the added service messages are classified, and the category information and the data table information are updated according to the information of the added service messages, so that the subsequent account checking is carried out on the payment system after the category information and the data table information are updated, the account checking efficiency can be improved, the expansibility of the payment system is improved, and the expansion cost is reduced.
Step S103, storing the service message of each category to a corresponding data table, and storing the service information to a preset message classification attribute table, wherein the service information comprises the information in the data table.
For example, in the embodiment of the present invention, the business information may include, but is not limited to, one or more of information in a data table, a business property, and a reconciliation element. The preset message classification attribute table can be preset by analyzing the existing service message, data table, account checking information and service type at the initial stage of starting account checking service of the payment system. The message classification attribute table can be dynamically updated according to the classification of the newly added service message, the change of the information such as the service elements, the data table and the like, so that the newly added service is conveniently stored, and the subsequent account checking is facilitated.
For example, the preset message classification attribute table may be modified according to a file or a related notification of a central bank or a central end of the payment system about a newly added service message. For example, when a central bank or a central end newly adds a service message, a red header file is issued to notify a commercial bank and a relevant document of the service message is issued, the embodiment of the present invention may classify the service message according to the received red header file and the relevant document of the service message, and modify a message classification attribute table according to the red header file and the relevant document, and may also manually classify the service message and modify the message classification attribute table to update information of the message classification attribute table for subsequent reconciliation.
For example, a method for setting a packet classification attribute table in the embodiment of the present invention is described in table 1 below.
TABLE 1
And step S104, after receiving an account checking notification sent by a center end of the payment system, receiving and storing account checking information sent by the center end, and performing account checking according to the account checking information and the message classification attribute table.
In the embodiment of the invention, the service messages are classified to obtain different types of service messages; constructing a corresponding data table according to different types of service messages; storing the service message of each category into a corresponding data table, and storing service information into a preset message classification attribute table, wherein the service information comprises information in the data table; after receiving an account checking notification sent by a center end of a payment system, receiving and storing account checking information sent by the center end, and performing account checking according to the account checking information and the message classification attribute table. The embodiment of the invention improves the account checking expansibility of the payment system and reduces the expansion cost by classifying the services, thereby having stronger usability and practicability.
Fig. 2 is a schematic flow chart of an implementation of a method for reconciliation of a payment system according to a second embodiment of the present invention, where as shown in fig. 2, the method may include the following steps:
step S201, classifying the service messages to obtain different types of service messages.
Step S202, constructing a corresponding data table according to the different types of service messages.
Step S203, storing the service message of each category to a corresponding data table, and storing the service information to a preset message classification attribute table, wherein the service information comprises the information in the data table.
Steps S201, S202, and S203 in this embodiment are the same as steps S101, S102, and S103, and specific reference may be made to the description of steps S101, S102, and S103, which is not repeated herein.
And step S204, receiving and storing reconciliation information sent by a center end of the payment system after receiving a reconciliation notice sent by the center end.
Step S205, classifying the reconciliation information; and comparing the classified account checking information with the service information stored in the message classification attribute table, and if the comparison result is consistent, finishing account checking.
The embodiment of the invention can analyze the type related to the account checking information by reading the information of the message classification attribute table, thereby classifying the account checking information.
Optionally, the reconciliation information and the service information of the related categories may be respectively counted and compared according to service summarizing factors such as the total initiating success count, the total initiating success amount, the total initiating failure count, the total initiating failure amount, the total receiving success count, the total receiving failure amount and the like, and if the comparison result is consistent, the reconciliation is completed.
Optionally, in the embodiment of the present invention, if the comparison result is inconsistent, performing detail checking on the reconciliation information in each category, and marking a reconciliation record of the reconciliation information and the service information, where the reconciliation record includes a record lacking information in the packet classification attribute table and/or a record of inconsistency between the service information and the reconciliation information.
Optionally, after the reconciliation record of the reconciliation information and the service information is marked, the message classification attribute table may be modified according to the reconciliation information; in addition, optionally, the message classification attribute table may also be modified manually according to the reconciliation information.
Optionally, if the message classification attribute table lacks information, the information lacking in the message classification attribute table is additionally recorded according to the reconciliation information, and reconciliation is performed again.
In the embodiment of the invention, the classified data granularity is much larger than that of a single stroke, and the same class has the same storage structure, so that batch comparison detailed records are facilitated, the check difficulty is reduced and the check efficiency is improved by classifying the service message and the check information and performing detailed check on the check information in each class.
In the embodiment of the invention, the service messages are classified to obtain different types of service messages; constructing a corresponding data table according to different types of service messages; storing the service message of each category into a corresponding data table, and storing service information into a preset message classification attribute table, wherein the service information comprises information in the data table; after receiving an account checking notification sent by a center end of a payment system, receiving and storing account checking information sent by the center end, and classifying the account checking information; and comparing the classified account checking information with the service information stored in the message classification attribute table, and if the comparison result is consistent, finishing account checking. The embodiment of the invention is convenient to acquire the storage information of the business in the account checking process by classifying the business message and storing the message classification attribute table, improves the checking efficiency by classifying the account checking information, and has the advantages of good system expansibility, high expansion efficiency and lower cost in expansion.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
Fig. 3 is a schematic diagram of a terminal device according to a fourth embodiment of the present invention, and only a part related to the fourth embodiment of the present invention is shown for convenience of description.
As shown in fig. 3, in the embodiment of the present invention, the apparatus 3 may include:
the classification module 31 is configured to classify the service packets to obtain service packets of different categories;
the processing module 32 is configured to construct a corresponding data table according to the different types of service messages;
the storage module 33 is configured to store the service packet of each category in a corresponding data table, and store service information in a preset packet classification attribute table, where the service information includes information in the data table;
the reconciliation module 34 is configured to receive and store reconciliation information sent by a center end of the payment system after receiving a reconciliation notification sent by the center end, and perform reconciliation according to the reconciliation information and the message classification attribute table.
Optionally, the reconciliation module 34 is specifically configured to:
classifying the reconciliation information; and comparing the classified account checking information with the service information stored in the message classification attribute table, and if the comparison result is consistent, finishing account checking.
Optionally, the reconciliation module 34 is further specifically configured to:
and if the comparison result is inconsistent, performing detail checking on the reconciliation information in each category, and marking the reconciliation records of the reconciliation information and the service information, wherein the reconciliation records comprise records lacking information in the message classification attribute table and/or records of inconsistency between the service information and the reconciliation information.
Optionally, the reconciliation module 34 is further specifically configured to: and modifying the message classification attribute table according to the account checking information.
Optionally, the reconciliation module 34 is further specifically configured to:
if the message classification attribute table lacks information, the information lacking in the message classification attribute table is added according to the account checking information, and account checking is carried out again.
Optionally, the apparatus 3 further comprises:
the updating module is used for determining the category of a new service message if the new service message is received, judging whether the category exists in the existing categories, and storing the new service message into a data table corresponding to the category if the category exists in the existing categories; if not, judging whether the existing data tables have the data tables meeting the preset conditions or not, if so, revising the data tables meeting the preset conditions according to preset rules, storing the new service message into the revised data tables, and updating the category information and the data table information; if the existing data table does not have a data table meeting the preset conditions, a corresponding new data table is created according to the category of the new service message, the new service message is stored in the new data table, and category information and data table information are updated.
Fig. 4 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in fig. 4, the terminal device 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42 stored in said memory 41 and executable on said processor 40. The processor 40, when executing the computer program 42, implements the steps in the various payment system reconciliation method embodiments described above, such as steps 101-104 shown in fig. 1. Alternatively, the processor 40, when executing the computer program 42, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the modules 31 to 34 shown in fig. 3.
Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to implement the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 42 in the terminal device 4. For example, the computer program 42 may be divided into a classification module, a processing module, a storage module, and a reconciliation module, and the specific functions of each module are as follows:
the classification module is used for classifying the service messages to obtain different types of service messages;
the processing module is used for constructing a corresponding data table according to the different types of service messages;
the storage module is used for storing the service message of each category into a corresponding data table and storing the service information into a preset message classification attribute table, wherein the service information comprises information in the data table;
and the reconciliation module is used for receiving and storing reconciliation information sent by the central end after receiving a reconciliation notice sent by the central end of the payment system, and performing reconciliation according to the reconciliation information and the message classification attribute table.
The terminal device 4 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 40, a memory 41. Those skilled in the art will appreciate that fig. 4 is merely an example of a terminal device 4 and does not constitute a limitation of terminal device 4 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the terminal device may also include input-output devices, network access devices, buses, etc.
The Processor 40 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 41 may be an internal storage unit of the terminal device 4, such as a hard disk or a memory of the terminal device 4. The memory 41 may also be an external storage device of the terminal device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the terminal device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the terminal device 4. The memory 41 is used for storing the computer program and other programs and data required by the terminal device. The memory 41 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. . Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (7)
1. A method of reconciling a payment system, comprising:
classifying the service messages to obtain different types of service messages;
constructing a corresponding data table according to different types of service messages;
storing the service message of each category into a corresponding data table, and storing service information into a preset message classification attribute table, wherein the service information comprises information in the data table;
after receiving an account checking notification sent by a center end of a payment system, receiving and storing account checking information sent by the center end, and performing account checking according to the account checking information and the message classification attribute table;
the reconciliation according to the reconciliation information and the message classification attribute table comprises the following steps:
classifying the reconciliation information;
comparing the classified account checking information with the service information stored in the message classification attribute table, and if the comparison result is consistent, finishing account checking;
after constructing the corresponding data table according to the different types of service messages, the method further comprises the following steps:
if a new service message is received, determining the category of the new service message, judging whether the category exists in the existing categories, and if so, storing the new service message into a data table corresponding to the category; if not, judging whether the existing data tables have the data tables meeting the preset conditions or not, if so, revising the data tables meeting the preset conditions according to preset rules, storing the new service message into the revised data tables, and updating the category information and the data table information; if the existing data table does not have a data table meeting the preset conditions, a corresponding new data table is created according to the category of the new service message, the new service message is stored in the new data table, and category information and data table information are updated.
2. The method of claim 1, wherein the method further comprises:
and if the comparison result is inconsistent, performing detail checking on the reconciliation information in each category, and marking the reconciliation records of the reconciliation information and the service information, wherein the reconciliation records comprise records lacking information in the message classification attribute table and/or records of inconsistency between the service information and the reconciliation information.
3. The method of claim 2, wherein after marking the reconciliation information with the reconciliation record for the business information, the method further comprises:
and modifying the message classification attribute table according to the account checking information.
4. The method of claim 2, wherein the method further comprises:
if the message classification attribute table lacks information, the information lacking in the message classification attribute table is added according to the account checking information, and account checking is carried out again.
5. An apparatus for reconciling a payment system, comprising:
the classification module is used for classifying the service messages to obtain different types of service messages;
the processing module is used for constructing a corresponding data table according to the different types of service messages;
the storage module is used for storing the service message of each category into a corresponding data table and storing the service information into a preset message classification attribute table, wherein the service information comprises information in the data table;
the reconciliation module is used for receiving and storing reconciliation information sent by a central end of the payment system after receiving a reconciliation notice sent by the central end, and performing reconciliation according to the reconciliation information and the message classification attribute table;
the updating module is used for determining the category of a new service message if the new service message is received, judging whether the category exists in the existing categories, and storing the new service message into a data table corresponding to the category if the category exists in the existing categories; if not, judging whether the existing data tables have the data tables meeting the preset conditions or not, if so, revising the data tables meeting the preset conditions according to preset rules, storing the new service message into the revised data tables, and updating the category information and the data table information; if the existing data table does not have a data table meeting the preset condition, creating a corresponding new data table according to the category of the new service message, storing the new service message to the new data table, and updating category information and data table information;
the reconciliation module is specifically configured to:
classifying the reconciliation information;
and comparing the classified account checking information with the service information stored in the message classification attribute table, and if the comparison result is consistent, finishing account checking.
6. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 4 when executing the computer program.
7. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810124678.9A CN108376364B (en) | 2018-02-07 | 2018-02-07 | Payment system account checking method and device and terminal device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810124678.9A CN108376364B (en) | 2018-02-07 | 2018-02-07 | Payment system account checking method and device and terminal device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108376364A CN108376364A (en) | 2018-08-07 |
| CN108376364B true CN108376364B (en) | 2021-08-20 |
Family
ID=63017573
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810124678.9A Active CN108376364B (en) | 2018-02-07 | 2018-02-07 | Payment system account checking method and device and terminal device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108376364B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109325028A (en) * | 2018-08-22 | 2019-02-12 | 平安普惠企业管理有限公司 | A kind of reconciliation file verification method and terminal device |
| CN109634950A (en) * | 2018-10-16 | 2019-04-16 | 深圳壹账通智能科技有限公司 | Service data management method, device, equipment and computer readable storage medium |
| CN109558756B (en) * | 2018-12-13 | 2022-04-12 | 艾体威尔电子技术(北京)有限公司 | EMV message analysis tool |
| CN109712035B (en) * | 2018-12-27 | 2021-03-26 | 北京百佑科技有限公司 | Property charging method and system based on current account system |
| CN110415095A (en) * | 2019-07-24 | 2019-11-05 | 深圳乐信软件技术有限公司 | A kind of account checking method, device, terminal and storage medium |
| CN111324623A (en) * | 2020-02-26 | 2020-06-23 | 深圳壹账通智能科技有限公司 | Resource transfer data checking method and device, computer equipment and storage medium |
| CN112785406B (en) * | 2021-02-03 | 2024-02-27 | 深圳乐信软件技术有限公司 | Account checking method, device, equipment and storage medium |
| CN113781033A (en) * | 2021-09-27 | 2021-12-10 | 中国银行股份有限公司 | Account separating method and device |
| CN114338850B (en) * | 2021-12-24 | 2024-03-19 | 百富计算机技术（深圳）有限公司 | Message checking method, device, terminal equipment and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103413216A (en) * | 2013-05-16 | 2013-11-27 | 深圳市淘淘谷信息技术有限公司 | Multi-account management payment method |
| CN107122434A (en) * | 2017-04-18 | 2017-09-01 | 北京思特奇信息技术股份有限公司 | A kind of method and system that reconciliation file is imported to database |
| CN107578329A (en) * | 2017-10-20 | 2018-01-12 | 中国银行股份有限公司 | Automatic account checking method and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050165681A1 (en) * | 2000-08-07 | 2005-07-28 | Tymetrix, Inc. | Method for automatic processing of invoices |
-
2018
- 2018-02-07 CN CN201810124678.9A patent/CN108376364B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103413216A (en) * | 2013-05-16 | 2013-11-27 | 深圳市淘淘谷信息技术有限公司 | Multi-account management payment method |
| CN107122434A (en) * | 2017-04-18 | 2017-09-01 | 北京思特奇信息技术股份有限公司 | A kind of method and system that reconciliation file is imported to database |
| CN107578329A (en) * | 2017-10-20 | 2018-01-12 | 中国银行股份有限公司 | Automatic account checking method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108376364A (en) | 2018-08-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108376364B (en) | Payment system account checking method and device and terminal device | |
| CN107800894B (en) | Intelligent voice prompt method and terminal equipment | |
| CN107784063B (en) | Algorithm generation method and terminal equipment | |
| CN113034274A (en) | Supply chain financial service system and method based on block chain and terminal equipment | |
| CN113093958B (en) | Data processing method and device and server | |
| US20130332374A1 (en) | Fraud prevention for real estate transactions | |
| CN108897729B (en) | Transaction template sharing method and device, electronic equipment and storage medium | |
| CN110942392A (en) | Service data processing method, device, equipment and medium | |
| CN113205402A (en) | Account checking method and device, electronic equipment and computer readable medium | |
| CN113129150A (en) | Transaction data processing method and device, terminal device and readable storage medium | |
| CN112434884A (en) | Method and device for establishing supplier classified portrait | |
| CN110335061B (en) | Transaction mode portrait establishing method, device, medium and electronic equipment | |
| CN111275071B (en) | Prediction model training method, prediction device and electronic equipment | |
| CN113034275A (en) | Management system and method based on block chain network and terminal equipment | |
| CN111832661A (en) | Classification model construction method and device, computer equipment and readable storage medium | |
| CN111105238A (en) | Transaction risk control method and device | |
| CN110659981A (en) | Enterprise dependency relationship identification method and device and electronic equipment | |
| CN107172311B (en) | Service evaluation method and terminal equipment | |
| CN116050359A (en) | Policy escrow entry method, system, terminal equipment and storage medium | |
| CN115689570A (en) | Business information risk identification method, device, equipment and medium | |
| CN113220687A (en) | Rule processing method, device and equipment | |
| CN113077234A (en) | Account checking method, device and storage medium | |
| CN112488557A (en) | Automatic calculation method, device and terminal based on grading standard objective scores | |
| CN115994743B (en) | Document abstract specification management method and system | |
| CN112131258B (en) | Data splicing method, device and equipment 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |