CN105279693B - A kind of method and system keeping cross-bank transaction account consistency - Google Patents
A kind of method and system keeping cross-bank transaction account consistency Download PDFInfo
- Publication number
- CN105279693B CN105279693B CN201510779175.1A CN201510779175A CN105279693B CN 105279693 B CN105279693 B CN 105279693B CN 201510779175 A CN201510779175 A CN 201510779175A CN 105279693 B CN105279693 B CN 105279693B
- Authority
- CN
- China
- Prior art keywords
- reconciliation
- account
- account status
- end system
- solicited 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
Landscapes
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
This application provides a kind of method and system of holding cross-bank transaction account consistency, this method comprises: the account transaction request information that real-time monitoring client initiates；After monitoring solicited message, the account status, for example of real time contrast's front-end system and the account status, for example of core system；When the account status, for example of the account status, for example and core system that find front-end system is inconsistent, starts the first update mode corresponding with the classification of solicited message and carry out reconciliation update；After front-end system is identical with the account status, for example of core system, start the second update mode corresponding with the classification of solicited message, reconciliation is carried out to front-end system and third party system and updates operation.This method passes through when client carries out cross-bank transaction business, reconciliation operation is carried out between the parties to front-end system, core system and third party system in real time, avoid the generation for causing tripartite, customer's account inconsistent that goes wrong due to some node, the real-time ensuring consistency of cross-bank transaction account.
Description
Technical field
This application involves bank transaction technical field more particularly to a kind of methods for keeping cross-bank transaction account consistency
And system.
Background technique
Proxy class system is a kind of relatively conventional system in banking system, such as agent bank's stock exchange transaction, Dai Liyin
Row forward exchange transaction acts on behalf of other bankings etc..With the rapidly development of financial industry, account transactions demand between cross-bank with
Increase, how efficiently and accurately to keep the account consistency between system is critical issue.
Currently, cross-bank transaction is by the way of: client is being asked by certain channel to front-end system initiation account transaction
It asks；After front-end system receives request, account business core billing and accounting system initiates account backward after completing a series of relevant treatments
Request；Front-end system receive core system treated response；Front-end system initiates transaction request to third party system；Preposition system
System receives the response that third party system returns；Former channel is returned after front-end system processing；Day carries out reconciliation processing eventually.
Therefore, because link needed for cross-bank is traded is more, if a certain node goes wrong, there is generation extensive unilateral
The possibility of account, and need to be handled after waiting DayEndProcess by manual intervention, cross-bank transaction account can not be thus kept in real time
Consistency.
Summary of the invention
In view of this, this application provides a kind of method and systems of holding cross-bank transaction account consistency, to overcome
The abnormal account of appearance is handled after can only waiting DayEndProcess by manual intervention in cross-bank transaction business in the prior art, can not
The problem of keeping the consistency of cross-bank transaction account in real time.
To achieve the above object, this application provides following technical schemes:
A method of keeping cross-bank transaction account consistency, comprising:
The account transaction request information that real-time monitoring client initiates；
After monitoring the solicited message, the account status, for example of real time contrast's front-end system and the book keeping operation shape of core system
State；
When the account status, for example of the account status, for example and the core system that find the front-end system is inconsistent, starting and institute
Corresponding first update mode of classification for stating solicited message carries out reconciliation update to the front-end system and the core system；
When the reconciliation update reach the front-end system it is identical with the account status, for example of the core system after, starting and institute
Corresponding second update mode of classification for stating solicited message carries out reconciliation to the front-end system and third party system and updates behaviour
Make.
Preferably, further includes: to the front-end system, the core system, the third party system tripartite book keeping operation shape
State carries out day secondary reconciliation eventually.
Preferably, the classification of the solicited message includes: deposit, withdraws the money or transfer accounts.
Preferably, corresponding with the classification of the solicited message the first update mode of the starting to the front-end system and
The core system carries out reconciliation update
When the solicited message is credit request information, by the account status, for example of the front-end system to the core system
Asynchronous interval is retransmitted, until the account status, for example of the two is identical；
When the solicited message is withdrawal request information, by the account status, for example of the front-end system to the core system
Asynchronous interval rushes just, until the account status, for example of the two is identical.
Preferably, starting second update mode corresponding with the classification of the solicited message, to the front-end system
Carrying out reconciliation update operation with third party system includes:
When the solicited message is credit request information, it is to the third party by the account status, for example of the front-end system
Unite asynchronous interval is retransmitted, until both account status, for example it is identical；
When the solicited message is withdrawal request information, it is to the third party by the account status, for example of the front-end system
Asynchronous interval punching unite just, until the account status, for example of the two is identical.
A kind of system keeping cross-bank transaction account consistency, comprising:
Monitoring unit, the account transaction request information initiated for real-time monitoring client；
Comparison unit, for after the monitoring unit monitors the solicited message, the note of real time contrast's front-end system
The account status, for example of account state and core system；
First reconciliation unit, for when the comparison unit find the front-end system account status, for example and the core system
When the account status, for example of system is inconsistent, start the first update mode corresponding with the classification of the solicited message to the front-end system
Reconciliation update is carried out with the core system；
Second reconciliation unit, the reconciliation update for carrying out when the first reconciliation unit reach the front-end system
After identical with the account status, for example of the core system, start the second update mode corresponding with the classification of the solicited message, it is right
The front-end system and third party system carry out reconciliation and update operation.
Preferably, further includes: end day reconciliation unit, for the front-end system, the core system, the third party
The account status, for example of system tripartite carries out day secondary reconciliation eventually.
Preferably, the classification of the solicited message includes: deposit, withdraws the money or transfer accounts.
Preferably, the first reconciliation unit includes: the first reconciliation subelement and the second reconciliation subelement, wherein
The first reconciliation subelement, for when the comparison unit find the account status, for example of the front-end system with it is described
When the account status, for example of core system is inconsistent, and when the solicited message is credit request information, by the front-end system
Account status, for example is retransmitted to the asynchronous interval of the core system, until the account status, for example of the two is identical；
The second reconciliation subelement, for when the comparison unit find the account status, for example of the front-end system with it is described
When the account status, for example of core system is inconsistent, and the solicited message be withdrawal request information when, by the note of the front-end system
Account state is rushed just to the asynchronous interval of the core system, until the account status, for example of the two is identical.
Preferably, the second reconciliation unit includes: third reconciliation subelement and the 4th reconciliation subelement, wherein
The third reconciliation subelement, for reaching the front-end system and the core system when the reconciliation updates
After account status, for example is identical, and when the solicited message is credit request information, by the account status, for example of the front-end system to described
The asynchronous interval of third party system is retransmitted, until the account status, for example of the two is identical；
The 4th reconciliation subelement, for reaching the front-end system and the core system when the reconciliation updates
After account status, for example is identical, and when the solicited message is withdrawal request information, by the account status, for example of the front-end system to described
The asynchronous interval of third party system rushes just, until the account status, for example of the two is identical.
From the above technical scheme, the application provides the method and system of holding cross-bank transaction account consistency,
By client carry out cross-bank transaction business when, in real time to front-end system, core system and third party system tripartite it
Between carry out reconciliation operation, in this way, not only avoiding going wrong due to some node causes tripartite and customer's account inconsistent
The generation of problem, and reduce manual intervention, the real-time ensuring consistency of cross-bank transaction account, makes the cross-bank of client
Transferred account service handles more quick convenience, enhances the Experience Degree of user.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
The embodiment of invention for those of ordinary skill in the art without creative efforts, can also basis
The attached drawing of offer obtains other attached drawings.
Fig. 1 is a kind of flow chart of the method for holding cross-bank transaction account consistency that the embodiment of the present application one provides；
Fig. 2 is a kind of flow chart of the method for holding cross-bank transaction account consistency that the embodiment of the present application two provides；
Fig. 3 is a kind of schematic diagram that carry out cross-bank is transferred accounts that the embodiment of the present application two provides；
Fig. 4 is a kind of structural representation of the system for holding cross-bank transaction account consistency that the embodiment of the present application three provides
Figure；
Fig. 5 is a kind of structural representation of the system for holding cross-bank transaction account consistency that the embodiment of the present application four provides
Figure.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, it is obtained by those of ordinary skill in the art without making creative efforts every other
Embodiment shall fall within the protection scope of the present invention.
Occur abnormal account in cross-bank transaction business to overcome in the prior art and can only wait after DayEndProcess by people
The problem of work intervention is handled, and can not keep the consistency of cross-bank transaction account in real time, this application provides a kind of holdings across silver
The method and system of row transaction account consistency, concrete scheme are as described below:
Embodiment one
The embodiment of the present application one provides a kind of method of holding cross-bank transaction account consistency, as shown in Figure 1, Fig. 1
A kind of holding cross-bank provided for the embodiment of the present application one trade account consistency method flow chart.This method comprises:
S101: the account transaction request information that real-time monitoring client initiates；
Client initiates account transaction request information in channel, which is sent to front-end system by channel.Pass through prison
Survey the account transaction request information that front-end system carrys out real-time monitoring client initiation.
S102: after monitoring solicited message, the account status, for example of real time contrast's front-end system and the book keeping operation shape of core system
State；
S103: when the account status, for example of the account status, for example and core system that find front-end system is inconsistent, starting and request
Corresponding first update mode of the classification of information carries out reconciliation update to front-end system and core system；
S104: when reconciliation update reach front-end system it is identical with the account status, for example of core system after, starting and solicited message
Corresponding second update mode of classification, reconciliation is carried out to front-end system and third party system and updates operation.
The embodiment of the present application one provide the holding cross-bank transaction account consistency method, by client carry out across
When bank transaction business, reconciliation operation is carried out between the parties to front-end system, core system and third party system in real time, this
Sample, not only avoiding going wrong due to some node leads to the generation of tripartite and customer's account inconsistence problems, but also drops
Low manual intervention, the real-time ensuring consistency of cross-bank transaction account, handles the cross-bank transferred account service of client more
It is quick convenient, enhance the Experience Degree of user.
Embodiment two
On the basis of example 1, the embodiment of the present application two provides a kind of more specifically holding cross-bank transaction account
The method of consistency, as shown in Fig. 2, Fig. 2 is a kind of holding cross-bank transaction account consistency that the embodiment of the present application two provides
Method flow chart.This method comprises:
S101: the account transaction request information that real-time monitoring client initiates；
Client initiates account transaction request information in channel, which is sent to front-end system by channel.Pass through prison
It surveys front-end system and carrys out the account transaction request information of real-time monitoring client initiation, and judge the classification of solicited message in order to subsequent
Reconciliation operation, wherein the classification of solicited message may include: deposit, withdraw the money or transfer accounts, and can also include other kinds of across silver
Row transaction business, in this application without limitation.
S102: after monitoring solicited message, the account status, for example of real time contrast's front-end system and the book keeping operation shape of core system
State；
S103: when the account status, for example of the account status, for example and core system that find front-end system is inconsistent, starting and request
Corresponding first update mode of the classification of information carries out reconciliation update to front-end system and core system；
In this application, start the first update mode corresponding with the classification of solicited message to front-end system and core system
Carrying out reconciliation update includes:
It is when solicited message is credit request information, the account status, for example of front-end system is heavy to the asynchronous interval of core system
Hair, until the account status, for example of the two is identical；
When solicited message is withdrawal request information, the account status, for example of front-end system is rushed to the asynchronous interval of core system
Just, until the account status, for example of the two is identical.
S104: when reconciliation update reach front-end system it is identical with the account status, for example of core system after, starting and solicited message
Corresponding second update mode of classification, reconciliation is carried out to front-end system and third party system and updates operation；
In this application, start the second update mode corresponding with the classification of solicited message, to front-end system and third party
System carries out reconciliation update operation
It is when solicited message is credit request information, the account status, for example of front-end system is heavy to the asynchronous interval of third party system
Hair, until the account status, for example of the two is identical；
When solicited message is withdrawal request information, the account status, for example of front-end system is rushed to the asynchronous interval of third party system
Just, until the account status, for example of the two is identical.
S105: day secondary reconciliation eventually is carried out to the account status, for example of front-end system, core system, third party system tripartite.
Day secondary reconciliation eventually is carried out to the account status, for example of front-end system, core system, third party system tripartite eventually by day,
Further ensure the consistency of three method, system account end-state.
Specifically, as shown in figure 3, Fig. 3 be the embodiment of the present application two provide it is a kind of using method described herein into
The schematic diagram that row cross-bank is transferred accounts.
(1) client initiates the account transaction of deposit to third party system:
When client is when channel initiates deposit transaction, channel sends the request to front-end system, and front-end system is properly received
The request of channel, whether inquiry savings account state is correct, and when customer deposit account state is correct, front-end system is to core system
System sends transaction request, preposition for the ease of handing over to client if final core system returns to abnormal due to the problems such as parsing
System returns to transaction successfully prompt to channel, and asynchronous real-time reconciliation module (trade by the holding cross-bank that i.e. the application is proposed
Hypostazation device corresponding to the method for account consistency) it can be according to front-end system account status, for example and core system account status, for example
Comparison, if the account status, for example of both discoveries is inconsistent, can asynchronous interval retransmit, until the account status, for example of the two is mutually all
Only, i.e. real-time query core system account status, for example, if local flowing water state be successfully and host to correspond to flowing water state be failure,
Former transaction is then initiated by asynchronous retransmission mechanism again, until success.At this point, asynchronous real-time reconciliation module can make preposition system
System continues interval and sends request to third party, until third party returns successfully.
(2) client initiates the account withdrawn the money transaction to third party system:
When client initiates withdrawal transaction in channel, channel sends the request to front-end system, and front-end system is properly received canal
The request in road, whether inquiry withdrawal account status is correct, and front-end system is returned to third party system transaction request, third party system
After success, front-end system core system initiates requests transaction, core system due to the problems such as parsing return it is abnormal, front-end system to
Channel returns to the prompt of Fail Transaction, and asynchronous real-time reconciliation module can be according to front-end system stateful transaction and core system state
Comparison, if the account status, for example of both discoveries is inconsistent, can the punching of asynchronous interval just, until the account status, for example of the two is mutually all
Only.That is real-time query core system account status, for example, if local flowing water state be failure and host to correspond to flowing water state be success,
It then rushes positive mechanism by asynchronous and is initiating former transaction punching again just, until host-flow water state is until failing.At this point, asynchronous real-time
Reconciliation module can make front-end system continue initiating asynchronous interval punching to third party system just, until success.
The method that this kind provided by the present application keeps cross-bank transaction account consistency, by becoming end day reconciliation processing
In the daytime real-time reconciliation is handled, and returns to the response results of front end when transaction occurs abnormal according to the selection of account type of transaction,
And subsequent punching is just or retransmission process so substantially increases system treatment effeciency, it eventually could be to different without waiting for day
Normal account is handled, and is reduced unnecessary manual intervention, is greatly improved user experience.
From the above technical scheme, the application provides the method and system of holding cross-bank transaction account consistency,
By client carry out cross-bank transaction business when, in real time to front-end system, core system and third party system tripartite it
Between carry out reconciliation operation, in this way, not only avoiding going wrong due to some node causes tripartite and customer's account inconsistent
The generation of problem, and reduce manual intervention, the real-time ensuring consistency of cross-bank transaction account, makes the cross-bank of client
Transferred account service handles more quick convenience, enhances the Experience Degree of user.
Embodiment three
On the basis of example 1, the embodiment of the present application three provides a kind of holding cross-bank transaction account consistency
System, as shown in figure 4, Fig. 4 is a kind of system for holding cross-bank transaction account consistency that the embodiment of the present application three provides
Structural schematic diagram.The system includes: monitoring unit 201, comparison unit 202, the first reconciliation unit 203 and the second reconciliation unit
204, wherein
Monitoring unit 201, the account transaction request information initiated for real-time monitoring client；
Client initiates account transaction request information in channel, which is sent to front-end system by channel.Pass through prison
Unit 201 is surveyed to monitor the account transaction request information that front-end system carrys out real-time monitoring client initiation.
Comparison unit 202, for after monitoring unit 201 monitors solicited message, the book keeping operation of real time contrast's front-end system
The account status, for example of state and core system；
First reconciliation unit 203, for finding the account status, for example of front-end system and the note of core system when comparison unit 202
When account state is inconsistent, starts the first update mode corresponding with the classification of solicited message and front-end system and core system are carried out
Reconciliation updates；
Second reconciliation unit 204, the reconciliation update for carrying out when the first reconciliation unit 203 reach front-end system and core
After the account status, for example of system is identical, start the second update mode corresponding with the classification of solicited message, to front-end system and third
Method, system carries out reconciliation and updates operation.
The system of holding cross-bank transaction account consistency provided in this embodiment, by carrying out cross-bank friendship in client
When easy business, reconciliation operation is carried out between the parties to front-end system, core system and third party system in real time, in this way, not
It only avoids going wrong due to some node and leads to the generation of tripartite and customer's account inconsistence problems, and reduce people
Work intervention, the consistency of real-time ensuring cross-bank transaction account, make the cross-bank transferred account service of client handle it is more quick just
Benefit enhances the Experience Degree of user.
Example IV
The embodiment of the present application four provides a kind of system for more specifically keeping cross-bank transaction account consistency, such as Fig. 5
Shown, Fig. 5 is a kind of structural schematic diagram of the system for holding cross-bank transaction account consistency that the embodiment of the present application four provides.
The system includes: monitoring unit 201, comparison unit 202, the first reconciliation unit 203, the second reconciliation unit 204 and the reconciliation of end day
Unit 205, wherein
Monitoring unit 201, the account transaction request information initiated for real-time monitoring client；
Client initiates account transaction request information in channel, which is sent to front-end system by channel.Pass through prison
Unit 201 is surveyed to monitor front-end system and carry out the account transaction request information of real-time monitoring client initiation, and judges solicited message
Classification operates in order to subsequent reconciliation, wherein the classification of solicited message may include: deposit, withdraw the money or transfer accounts, and can also include
Other kinds of cross-bank transaction business, in this application without limitation.
Comparison unit 202, for after monitoring unit 201 monitors solicited message, the book keeping operation of real time contrast's front-end system
The account status, for example of state and core system；
First reconciliation unit 203, for finding the account status, for example of front-end system and the note of core system when comparison unit 202
When account state is inconsistent, starts the first update mode corresponding with the classification of solicited message and front-end system and core system are carried out
Reconciliation updates；
In this application, the first reconciliation unit includes: the first reconciliation subelement and the second reconciliation subelement, wherein
First reconciliation subelement, for when the account status, for example of comparison unit discovery front-end system and the book keeping operation shape of core system
When state is inconsistent, and when solicited message is credit request information, by the account status, for example of front-end system to core system asynchronous
Every repeating transmission, until the account status, for example of the two is identical；
Second reconciliation subelement, for when the account status, for example of comparison unit discovery front-end system and the book keeping operation shape of core system
When state is inconsistent, and when solicited message is withdrawal request information, by the account status, for example of front-end system to the asynchronous interval of core system
It rushes just, until the account status, for example of the two is identical.
Second reconciliation unit 204, the reconciliation update for carrying out when the first reconciliation unit 203 reach front-end system and core
After the account status, for example of system is identical, start the second update mode corresponding with the classification of solicited message, to front-end system and third
Method, system carries out reconciliation and updates operation；
In this application, the second reconciliation unit includes: third reconciliation subelement and the 4th reconciliation subelement, wherein
Third reconciliation subelement, for when reconciliation update reach front-end system it is identical with the account status, for example of core system after,
And solicited message is retransmitted the account status, for example of front-end system to the asynchronous interval of third party system when being credit request information, up to
The account status, for example of the two is identical；
4th reconciliation subelement, for when reconciliation update reach front-end system it is identical with the account status, for example of core system after,
And solicited message is when being withdrawal request information, just to the punching of third party system asynchronous interval by the account status, for example of front-end system, up to
The account status, for example of the two is identical.
Day whole reconciliation unit 205, for day eventually to front-end system, core system, third party system tripartite book keeping operation shape
State carries out day secondary reconciliation eventually.
In this application, end day reconciliation unit can be carried out by the first reconciliation unit and the second reconciliation unit in day eventually
It is secondary right eventually to carry out day to the account status, for example of front-end system, core system, third party system tripartite eventually by day for secondary reconciliation
Account further ensures the consistency of three method, system account end-state.
Specifically, can mutually refer to, repeat no more in this application with place the same or similar in other embodiments.
The system of holding cross-bank transaction account consistency provided in this embodiment, by carrying out cross-bank friendship in client
When easy business, reconciliation operation is carried out between the parties to front-end system, core system and third party system in real time, in this way, not
It only avoids going wrong due to some node and leads to the generation of tripartite and customer's account inconsistence problems, and reduce people
Work intervention, the consistency of real-time ensuring cross-bank transaction account, make the cross-bank transferred account service of client handle it is more quick just
Benefit enhances the Experience Degree of user.
Finally, it is to be noted that, herein, relational terms such as first and second and the like be used merely to by
One entity or operation are distinguished with another entity or operation, without necessarily requiring or implying these entities or operation
Between there are any actual relationship or orders.Moreover, the terms "include", "comprise" or its any other variant meaning
Covering non-exclusive inclusion, so that the process, method, article or equipment for including a series of elements not only includes that
A little elements, but also including other elements that are not explicitly listed, or further include for this process, method, article or
The intrinsic element of equipment.In the absence of more restrictions, the element limited by sentence "including a ...", is not arranged
Except there is also other identical elements in the process, method, article or apparatus that includes the element.
Each embodiment in this specification is described in a progressive manner, the highlights of each of the examples are with other
The difference of embodiment, the same or similar parts in each embodiment may refer to each other.
The foregoing description of the disclosed embodiments makes professional and technical personnel in the field can be realized or use the application.
Various modifications to these embodiments will be readily apparent to those skilled in the art, as defined herein
General Principle can be realized in other embodiments without departing from the spirit or scope of the application.Therefore, the application
It is not intended to be limited to the embodiments shown herein, and is to fit to and the principles and novel features disclosed herein phase one
The widest scope of cause.
Claims (10)
1. a kind of method for keeping cross-bank transaction account consistency characterized by comprising
The account transaction request information that real-time monitoring client initiates；
After monitoring the solicited message, the account status, for example of real time contrast's front-end system and the account status, for example of core system；
When the account status, for example of the account status, for example and the core system that find the front-end system is inconsistent, starting is asked with described
Corresponding first update mode of the classification of information is asked to carry out reconciliation update to the front-end system and the core system；
When the reconciliation update reach the front-end system it is identical with the account status, for example of the core system after, starting asked with described
Corresponding second update mode of the classification of information is sought, reconciliation is carried out to the front-end system and third party system and updates operation.
2. the method according to claim 1 for keeping cross-bank transaction account consistency, which is characterized in that further include: it is right
The front-end system, the core system, the account status, for example of the third party system tripartite carry out day secondary reconciliation eventually.
3. the method according to claim 1 for keeping cross-bank transaction account consistency, which is characterized in that the request letter
The classification of breath includes: deposit, withdraws the money or transfer accounts.
4. it is according to claim 1 keep cross-bank transaction account consistency method, which is characterized in that it is described starting with
Corresponding first update mode of the classification of the solicited message carries out reconciliation update to the front-end system and the core system
Include:
It is when the solicited message is credit request information, the account status, for example of the front-end system is asynchronous to the core system
Interval is retransmitted, until the account status, for example of the two is identical；
It is when the solicited message is withdrawal request information, the account status, for example of the front-end system is asynchronous to the core system
Interval rushes just, until the account status, for example of the two is identical.
5. it is according to claim 1 keep cross-bank transaction account consistency method, which is characterized in that it is described starting with
Corresponding second update mode of the classification of the solicited message carries out reconciliation to the front-end system and third party system and updates behaviour
Work includes:
It is when the solicited message is credit request information, the account status, for example of the front-end system is different to the third party system
Step interval is retransmitted, until the account status, for example of the two is identical；
It is when the solicited message is withdrawal request information, the account status, for example of the front-end system is different to the third party system
Step interval rushes just, until the account status, for example of the two is identical.
6. a kind of system for keeping cross-bank transaction account consistency characterized by comprising
Monitoring unit, the account transaction request information initiated for real-time monitoring client；
Comparison unit, for after the monitoring unit monitors the solicited message, the book keeping operation shape of real time contrast's front-end system
The account status, for example of state and core system；
First reconciliation unit, for finding the account status, for example and the core system of the front-end system when the comparison unit
When account status, for example is inconsistent, start the first update mode corresponding with the classification of the solicited message to the front-end system and institute
It states core system and carries out reconciliation update；
Second reconciliation unit, the reconciliation update for carrying out when the first reconciliation unit reach the front-end system and institute
State core system account status, for example it is identical after, start corresponding with the classification of the solicited message the second update mode, to described
Front-end system and third party system carry out reconciliation and update operation.
7. the system according to claim 6 for keeping cross-bank transaction account consistency, which is characterized in that further include: day
Whole reconciliation unit carries out day for the account status, for example to the front-end system, the core system, the third party system tripartite
Secondary reconciliation eventually.
8. the system according to claim 6 for keeping cross-bank transaction account consistency, which is characterized in that the request letter
The classification of breath includes: deposit, withdraws the money or transfer accounts.
9. the system according to claim 6 for keeping cross-bank transaction account consistency, which is characterized in that described first pair
Bill member includes: the first reconciliation subelement and the second reconciliation subelement, wherein
The first reconciliation subelement, for finding the account status, for example and the core of the front-end system when the comparison unit
When the account status, for example of system is inconsistent, and when the solicited message is credit request information, by the book keeping operation of the front-end system
State is retransmitted to the asynchronous interval of the core system, until the account status, for example of the two is identical；
The second reconciliation subelement, for finding the account status, for example and the core of the front-end system when the comparison unit
When the account status, for example of system is inconsistent, and the solicited message be withdrawal request information when, by the book keeping operation shape of the front-end system
State is rushed just to the asynchronous interval of the core system, until the account status, for example of the two is identical.
10. the system according to claim 6 for keeping cross-bank transaction account consistency, which is characterized in that described second
Reconciliation unit includes: third reconciliation subelement and the 4th reconciliation subelement, wherein
The third reconciliation subelement, for reaching the book keeping operation of the front-end system and the core system when reconciliation update
After state is identical, and when the solicited message is credit request information, by the account status, for example of the front-end system to the third
The asynchronous interval of method, system is retransmitted, until the account status, for example of the two is identical；
The 4th reconciliation subelement, for reaching the book keeping operation of the front-end system and the core system when reconciliation update
After state is identical, and when the solicited message is withdrawal request information, by the account status, for example of the front-end system to the third
The asynchronous interval of method, system rushes just, until the account status, for example of the two is identical.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510779175.1A CN105279693B (en) | 2015-11-13 | 2015-11-13 | A kind of method and system keeping cross-bank transaction account consistency |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510779175.1A CN105279693B (en) | 2015-11-13 | 2015-11-13 | A kind of method and system keeping cross-bank transaction account consistency |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105279693A CN105279693A (en) | 2016-01-27 |
| CN105279693B true CN105279693B (en) | 2019-03-12 |
Family
ID=55148648
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510779175.1A Active CN105279693B (en) | 2015-11-13 | 2015-11-13 | A kind of method and system keeping cross-bank transaction account consistency |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105279693B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI820556B (en) * | 2021-12-30 | 2023-11-01 | 財金資訊股份有限公司 | Fund transfer automatic accounting system and method |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106600251A (en) * | 2016-11-30 | 2017-04-26 | 深圳维恩贝特科技股份有限公司 | Internet finance data interaction method, device and system |
| CN107798593B (en) * | 2017-11-07 | 2021-08-13 | 泰康保险集团股份有限公司 | Financial data processing method, device, medium and electronic equipment |
| CN107909460B (en) * | 2017-12-11 | 2022-01-11 | 深圳前海微众银行股份有限公司 | Position synchronization method, device, data center and storage medium |
| CN109034769B (en) * | 2018-07-03 | 2022-07-05 | 中国银行股份有限公司 | Transaction data processing method and device, storage medium and electronic equipment |
| CN109523378B (en) * | 2018-10-22 | 2021-03-23 | 中国银行股份有限公司 | Method, device and system for maintaining transaction consistency |
| CN110472956B (en) * | 2019-08-16 | 2022-04-12 | 中国银行股份有限公司 | Real-time detection method and device for split-payment behavior |
| CN110619570B (en) * | 2019-09-19 | 2022-02-01 | 中国银行股份有限公司 | Cross-bank transfer processing method and device |
| CN111026769B (en) * | 2019-10-16 | 2023-04-18 | 平安科技（深圳）有限公司 | Working method of dual-core front-end system and related equipment thereof |
| CN113554498B (en) * | 2020-04-08 | 2024-03-19 | 中国移动通信集团广东有限公司 | Processing method and device for user account request |
| CN112053232B (en) * | 2020-09-03 | 2023-09-22 | 中国银行股份有限公司 | Self-service equipment business accounting consistency processing method and device |
| CN113032176A (en) * | 2021-03-23 | 2021-06-25 | 中国邮政储蓄银行股份有限公司 | Distributed transaction double-compensation method and device based on daily account checking |
| CN112965986B (en) * | 2021-03-30 | 2024-05-28 | 建信金融科技有限责任公司 | Service consistency processing method, device, equipment and storage medium |
| CN113313593B (en) * | 2021-06-23 | 2024-01-30 | 中国农业银行股份有限公司 | Data processing method and data processing device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101877158A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Front service platform of bank and operation processing method thereof |
| CN101877099A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Day-end processing module based on bank preposing service platforms and application method thereof |
-
2015
- 2015-11-13 CN CN201510779175.1A patent/CN105279693B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101877158A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Front service platform of bank and operation processing method thereof |
| CN101877099A (en) * | 2010-03-23 | 2010-11-03 | 苏州德融嘉信信用管理技术有限公司 | Day-end processing module based on bank preposing service platforms and application method thereof |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI820556B (en) * | 2021-12-30 | 2023-11-01 | 財金資訊股份有限公司 | Fund transfer automatic accounting system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105279693A (en) | 2016-01-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105279693B (en) | A kind of method and system keeping cross-bank transaction account consistency | |
| CN110363665B (en) | Credit right data processing method, device, equipment and medium | |
| CN107169749B (en) | Network payment reconciliation method and system | |
| CN100452707C (en) | A method and system for keeping data consistency | |
| US8458064B1 (en) | System and method for transferring electronic account information | |
| CN109523378B (en) | Method, device and system for maintaining transaction consistency | |
| US20150095221A1 (en) | Systems and Methods for Activating Electronic Bill Presentment | |
| CN109034769B (en) | Transaction data processing method and device, storage medium and electronic equipment | |
| US8924456B2 (en) | Method and system for processing online joint guarantee | |
| CN109859043B (en) | Transaction clearing method and transaction clearing system | |
| JP6218979B1 (en) | Financial transaction method and system using blockchain | |
| CN106097092A (en) | Data processing method and device for reconciliation | |
| CN111026769B (en) | Working method of dual-core front-end system and related equipment thereof | |
| CN101281636A (en) | Method and system for distributing cards automatically | |
| CN108762895B (en) | Method and device for processing distributed transaction | |
| CN109584060A (en) | Processing method, device and the computer equipment and storage medium of timing transaction task | |
| CN110490584A (en) | Transaction processing method, device, system, computer equipment and medium | |
| CN110910106B (en) | Cash management message processing method and system | |
| US9059908B2 (en) | Method and system for facilitating non-interruptive transactions | |
| CN106557921A (en) | On-line payment method and device | |
| CN103927825A (en) | Self-help paper bill processing and checking system and application method thereof | |
| CN107944850A (en) | Fixed account dump method and device | |
| KR101270760B1 (en) | System and method of managing automatic withdrawal | |
| TW202013276A (en) | Transaction processing method and device, electronic equipment and computer readable storage medium | |
| US20200202437A1 (en) | Blockchain-based settlement method, apparatus, and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |