CN112529556A - Securities account-marking and registering method and system - Google Patents

Securities account-marking and registering method and system Download PDF

Info

Publication number
CN112529556A
CN112529556A CN202011467374.6A CN202011467374A CN112529556A CN 112529556 A CN112529556 A CN 112529556A CN 202011467374 A CN202011467374 A CN 202011467374A CN 112529556 A CN112529556 A CN 112529556A
Authority
CN
China
Prior art keywords
account
marking
security
module
carried out
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011467374.6A
Other languages
Chinese (zh)
Inventor
丁伟
肖建杰
张东哲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Fandi Information Technology Co ltd
Original Assignee
Shanghai Fandi Information Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Fandi Information Technology Co ltd filed Critical Shanghai Fandi Information Technology Co ltd
Priority to CN202011467374.6A priority Critical patent/CN112529556A/en
Publication of CN112529556A publication Critical patent/CN112529556A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108Remote banking, e.g. home banking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The invention provides a method and a system for checking and registering securities, comprising the following steps: step M1: establishing reliable and long connection with the stock platform and the futures counter through a socket, keeping heartbeat, and recovering the connection when the counter platform is restarted; step M2: respectively sending request messages to a security platform and a futures counter through a pb protocol and an xml protocol; step M3: and receiving the request message, performing account division operation, generating a unique main/sub flow number for each account division, and storing the flow number into the MySQL database. The invention ensures the idempotent and the safety of the fund transfer interface by adopting a token and signature verification mechanism.

Description

Securities account-marking and registering method and system
Technical Field
The invention relates to the technical field of computer data processing, in particular to a method and a system for checking and registering securities accounts, and more particularly relates to a Fangde checking and registering platform.
Background
At present, the transaction volume and the transaction speed of a plurality of services which are planned in real time are very high, and in the process of restarting and deploying an application server, a request in the time period is often not processed, that is, a part of the processing of the services is inevitably lost in the process of restarting and deploying, so that the services fail.
Patent document CN107833030A (application number: 201711061948.8) discloses a bank cache account-based account-dividing method and device, which obtains the non-in-transit successful transaction information of each third-party company; identifying third party corporate identification information in the non-successful-in-transit transaction information; dividing the non-in-transit successful transaction information into a plurality of groups according to the identification information of the third party company; each group of divided non-in-transit successful transaction information respectively corresponds to third party company identification information; the identification information of the third party company corresponding to the non-in-transit successful transaction information of different groups is different; carrying out rolling difference processing on each group of non-in-transit successful transaction information to obtain rolling difference statistical information of each third-party company; and performing account marking processing from the main line cache account of each third-party company according to the rolling difference statistical information.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a security ledger registration method and a security ledger registration system.
The invention provides a security accounting and registering method, which comprises the following steps:
step M1: establishing credible long connection with the security platform and the futures counter through a socket and keeping heartbeat, and when the security platform and the futures counter are restarted, restoring the connection;
step M2: respectively sending request messages to a security platform and a futures counter through a pb protocol and an xml protocol;
step M3: and receiving the request message, performing account division operation, generating a unique main/sub flow number for each account division, and storing the flow number into the MySQL database.
Preferably, the step M3 includes:
step M3.1: checking the account-marking interface and verifying the idempotency;
step M3.2: after the verification is passed, account marking is carried out according to user fund accounts at counters at two ends of the account marking direction, and when the time length of account marking processing exceeds the preset time or an error code which cannot be confirmed is returned, the account marking state is marked, and an alarm mechanism is triggered; when the account marking fails and returns a preset error code, a retry processing mechanism is carried out, the account marking processing is repeatedly carried out for a preset number of times, and when the account marking still fails after retry, the operation of correcting the account and returning to the original account is carried out, the account marking state is recorded, and the fund of the user is ensured to be correct;
step M3.3: when the serial number is stored in the MySQL database and the failure is abnormal, the local disk file is recorded in a file writing mode, and the file is read through the timing script to try to perform warehousing operation again.
Preferably, the step M3,1 includes: and the security verification and the idempotent verification of the account-marking interface are realized through a token and a parameter signature verification mechanism.
Preferably, the triggering an alarm mechanism in step M3.2 includes: the prompt of the number of records of the tab page and/or the red point is sent by short messages and mails and is confirmed and processed manually.
The invention provides a stock accounting and registering system, which comprises:
module M1: establishing credible long connection with the security platform and the futures counter through a socket and keeping heartbeat, and when the security platform and the futures counter are restarted, restoring the connection;
module M2: respectively sending request messages to a security platform and a futures counter through a pb protocol and an xml protocol;
module M3: and receiving the request message, performing account division operation, generating a unique main/sub flow number for each account division, and storing the flow number into the MySQL database.
Preferably, said module M3 comprises:
module M3.1: checking the account-marking interface and verifying the idempotency;
module M3.2: after the verification is passed, account marking is carried out according to user fund accounts at counters at two ends of the account marking direction, and when the time length of account marking processing exceeds the preset time or an error code which cannot be confirmed is returned, the account marking state is marked, and an alarm mechanism is triggered; when the account marking fails and returns a preset error code, a retry processing mechanism is carried out, the account marking processing is repeatedly carried out for a preset number of times, and when the account marking still fails after retry, the operation of correcting the account and returning to the original account is carried out, the account marking state is recorded, and the fund of the user is ensured to be correct;
module M3.3: when the serial number is stored in the MySQL database and the failure is abnormal, the local disk file is recorded in a file writing mode, and the file is read through the timing script to try to perform warehousing operation again.
Preferably, said module M3,1 comprises: the security verification and the idempotent verification of the account-marking interface are realized through a token and a parameter signature verification mechanism;
the triggering alarm mechanism in the module M3.2 comprises: the prompt of the number of records of the tab page and/or the red point is sent by short messages and mails and is confirmed and processed manually.
Preferably, the method further comprises the following steps: and multiple query conditions are supported to query each stroke of account flow records and account division states in the MySQL database.
Preferably, the method further comprises the following steps: and settling the account-dividing running water at regular time every day to generate a daily statement, comparing and checking the daily running water uploaded to the two counters with the running water in the MySQL database, and generating a bad account record for manual operation and comparison aiming at the data which cannot be compared.
Preferably, the method further comprises the following steps: and performing authority management setting based on the rbac, and endowing different background users with different roles and different operation authorities by an administrator with fine granularity.
Compared with the prior art, the invention has the following beneficial effects:
1. the invention ensures the idempotent and the safety of the fund transfer interface by adopting a token plus signature verification mechanism;
2. the invention solves the problem that the availability of the fund transfer function is ensured under the scenes that the fund counter service of two parties breaks down in a short time or has network problems and the like by a mode of retrying when the fund transfer is failed to transfer out;
3. the invention ensures the correctness of account funds by adopting the function of automatically correcting the transferred failure system under the condition that the user does not sense;
4. by adopting the functions of manual correction and an alarm mechanism of the transfer-in failure system, when the fund counter goes out of a problem, the problem of user fund is solved, manual intervention is timely carried out, and the fund correctness of the user is ensured.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments with reference to the following drawings:
FIG. 1 is a schematic diagram of a security ledger registration system;
fig. 2 is a flowchart of a billing registration method.
Detailed Description
The present invention will be described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the invention, but are not intended to limit the invention in any way. It should be noted that it would be obvious to those skilled in the art that various changes and modifications can be made without departing from the spirit of the invention. All falling within the scope of the present invention.
Example 1
The invention provides a security accounting and registering method, which comprises the following steps:
step M1: establishing credible long connection with the security platform and the futures counter through a socket and keeping heartbeat, and when the security platform and the futures counter are restarted, restoring the connection;
step M2: respectively sending request messages to a security platform and a futures counter through a pb protocol and an xml protocol;
step M3: and receiving the request message, performing account division operation, generating a unique main/sub flow number for each account division, and storing the flow number into the MySQL database.
Specifically, the step M3 includes:
step M3.1: checking the account-marking interface and verifying the idempotency;
step M3.2: after the verification is passed, account marking is carried out according to user fund accounts at counters at two ends of the account marking direction, and when the time length of account marking processing exceeds the preset time or an error code which cannot be confirmed is returned, the account marking state is marked, and an alarm mechanism is triggered; when the account marking fails and returns a preset error code, a retry processing mechanism is carried out, the account marking processing is repeatedly carried out for a preset number of times, and when the account marking still fails after retry, the operation of correcting the account and returning to the original account is carried out, the account marking state is recorded, and the fund of the user is ensured to be correct;
step M3.3: when the serial number is stored in the MySQL database and the failure is abnormal, the local disk file is recorded in a file writing mode, and the file is read through the timing script to try to perform warehousing operation again.
Specifically, the step M3,1 includes: and the security verification and the idempotent verification of the account-marking interface are realized through a token and a parameter signature verification mechanism.
Specifically, the triggering of the alarm mechanism in step M3.2 includes: the prompt of the number of records of the tab page and/or the red point is sent by short messages and mails and is confirmed and processed manually.
The invention provides a stock accounting and registering system, which comprises:
module M1: establishing credible long connection with the security platform and the futures counter through a socket and keeping heartbeat, and when the security platform and the futures counter are restarted, restoring the connection;
module M2: respectively sending request messages to a security platform and a futures counter through a pb protocol and an xml protocol;
module M3: and receiving the request message, performing account division operation, generating a unique main/sub flow number for each account division, and storing the flow number into the MySQL database.
Specifically, the module M3 includes:
module M3.1: checking the account-marking interface and verifying the idempotency;
module M3.2: after the verification is passed, account marking is carried out according to user fund accounts at counters at two ends of the account marking direction, and when the time length of account marking processing exceeds the preset time or an error code which cannot be confirmed is returned, the account marking state is marked, and an alarm mechanism is triggered; when the account marking fails and returns a preset error code, a retry processing mechanism is carried out, the account marking processing is repeatedly carried out for a preset number of times, and when the account marking still fails after retry, the operation of correcting the account and returning to the original account is carried out, the account marking state is recorded, and the fund of the user is ensured to be correct;
module M3.3: when the serial number is stored in the MySQL database and the failure is abnormal, the local disk file is recorded in a file writing mode, and the file is read through the timing script to try to perform warehousing operation again.
In particular, said module M3,1 comprises: the security verification and the idempotent verification of the account-marking interface are realized through a token and a parameter signature verification mechanism;
the triggering alarm mechanism in the module M3.2 comprises: the prompt of the number of records of the tab page and/or the red point is sent by short messages and mails and is confirmed and processed manually.
Specifically, the method further comprises the following steps: and multiple query conditions are supported to query each stroke of account flow records and account division states in the MySQL database.
Specifically, the method further comprises the following steps: and settling the account-dividing running water at regular time every day to generate a daily statement, comparing and checking the daily running water uploaded to the two counters with the running water in the MySQL database, and generating a bad account record for manual operation and comparison aiming at the data which cannot be compared.
Specifically, the method further comprises the following steps: and performing authority management setting based on the rbac, and endowing different background users with different roles and different operation authorities by an administrator with fine granularity.
Example 2
Example 2 is a modification of example 1
The invention provides a stock accounting and registering method, as shown in figure 1, comprising:
step M1: and establishing a credible long connection with the Fangde securities and the futures counter through the socket, keeping the heartbeat, and supporting automatic connection recovery when the counter end is restarted.
Step M2: respectively sending request messages to securities and a futures counter through a pb protocol and an xml protocol, and packaging the request messages into an external app end account-marking interface;
step M3: a unique master/sub journal number is generated by billing each time and the information is entered into the MySQL database.
Step M2 then includes:
step M2.1: checking the account-marking interface and verifying the idempotency;
step M2.2: after the verification is passed, the user fund accounts of the counters at the two ends are divided according to the dividing direction, when the dividing processing time length exceeds the preset time or an error code which cannot be confirmed is returned, the dividing state is marked specially, an alarm mechanism is triggered to send a short message and a mail, and the manual confirmation processing is needed; and when the account marking fails and a specific error code is returned, a retry processing mechanism is carried out, the account marking is carried out for 3 times again, if the account marking still fails after retry, the system automatically corrects the original account and records the account marking state, and the fund of the user is ensured to be correct.
Step M2.3: when failure and abnormity of MySQL are caused when data is recorded, a local disk file is recorded in a file writing mode, and then a file is read through a timing script to try to perform warehousing operation again.
The fund conversion function between the securities and the futures counter of the user is realized through the above mode, and a system-level exception handling scheme, namely a system automatic correction mechanism, is provided according to a specific error code returned by the counter; and providing a system short message and mail alarm mechanism and a manual-level manual correction processing mechanism once the error codes which cannot be processed appear and the appointed system processing time is exceeded.
The ledger registration platform, as shown in fig. 2, mainly includes:
external Api:
mainly relate to and draw the account function: the method is characterized in that long connection is established with securities and a futures counter through a socket, heartbeat is kept, details are realized mainly by shielding a bottom layer on an application end, and a packaged public api interface is externally provided to realize a one-key account marking function. The method comprises the steps of realizing security verification and idempotent verification of an account-marking interface through a token and a parameter signature verification mechanism; overtime processing, failure retry and automatic correction operation; short message and mail warning function. And generating flow records of each stroke account flow and recording the flow records into the MySQL database, supporting file writing operation when the database fails to write, and recovering the file to the database at a later time to prevent data loss.
A background management system:
a user authority module: and performing authority management design based on the rbac, and endowing different background users with different roles and different operation authorities by an administrator with fine granularity. Such as giving a certain service person a manual processing correction authority, a manual reconciliation authority, etc.
The flow module: and multiple inquiry conditions (in different conditions such as account marking direction, amount, account and the like) are supported to inquire the flow record and the account marking state of each stroke of the system.
A settlement module: and carrying out batch running on the daily timing script to settle daily billing running water to generate a daily statement. And provide the check account function to the backstage personnel: through uploading daily running water of the two counters, the system automatically checks accounts by comparing the running water with the running water of the system, and generates bad account records for manual operation and comparison aiming at data which cannot be compared.
Early warning: and the record aiming at the account-dividing failure of the application end can be displayed on an early warning tab page and a red point record number prompt, so that a background manager can conveniently know the user with the account-dividing failure in real time and perform manual intervention, and perform manual correction or manual continuous transfer to a function.
Those skilled in the art will appreciate that, in addition to implementing the systems, apparatus, and various modules thereof provided by the present invention in purely computer readable program code, the same procedures can be implemented entirely by logically programming method steps such that the systems, apparatus, and various modules thereof are provided in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Therefore, the system, the device and the modules thereof provided by the present invention can be considered as a hardware component, and the modules included in the system, the device and the modules thereof for implementing various programs can also be considered as structures in the hardware component; modules for performing various functions may also be considered to be both software programs for performing the methods and structures within hardware components.
The foregoing description of specific embodiments of the present invention has been presented. It is to be understood that the present invention is not limited to the specific embodiments described above, and that various changes or modifications may be made by one skilled in the art within the scope of the appended claims without departing from the spirit of the invention. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.

Claims (10)

1. A method of stock ledger registration, comprising:
step M1: establishing credible long connection with the security platform and the futures counter through a socket and keeping heartbeat, and when the security platform and the futures counter are restarted, restoring the connection;
step M2: respectively sending request messages to a security platform and a futures counter through a pb protocol and an xml protocol;
step M3: and receiving the request message, performing account division operation, generating a unique main/sub flow number for each account division, and storing the flow number into the MySQL database.
2. The security ledger-registration method according to claim 1, characterized in that said step M3 comprises:
step M3.1: checking the account-marking interface and verifying the idempotency;
step M3.2: after the verification is passed, account marking is carried out according to user fund accounts at counters at two ends of the account marking direction, and when the time length of account marking processing exceeds the preset time or an error code which cannot be confirmed is returned, the account marking state is marked, and an alarm mechanism is triggered; when the account marking fails and returns a preset error code, a retry processing mechanism is carried out, the account marking processing is repeatedly carried out for a preset number of times, and when the account marking still fails after retry, the operation of correcting the account and returning to the original account is carried out, the account marking state is recorded, and the fund of the user is ensured to be correct;
step M3.3: when the serial number is stored in the MySQL database and the failure is abnormal, the local disk file is recorded in a file writing mode, and the file is read through the timing script to try to perform warehousing operation again.
3. The security ledger-check-in method according to claim 2, characterized in that said step M3,1 comprises: and the security verification and the idempotent verification of the account-marking interface are realized through a token and a parameter signature verification mechanism.
4. The security cross-check entry method of claim 2, wherein said triggering an alarm mechanism in step M3.2 comprises: the prompt of the number of records of the tab page and/or the red point is sent by short messages and mails and is confirmed and processed manually.
5. A security ledger registration system, comprising:
module M1: establishing credible long connection with the security platform and the futures counter through a socket and keeping heartbeat, and when the security platform and the futures counter are restarted, restoring the connection;
module M2: respectively sending request messages to a security platform and a futures counter through a pb protocol and an xml protocol;
module M3: and receiving the request message, performing account division operation, generating a unique main/sub flow number for each account division, and storing the flow number into the MySQL database.
6. The security cross-check entry system of claim 5 wherein said module M3 comprises:
module M3.1: checking the account-marking interface and verifying the idempotency;
module M3.2: after the verification is passed, account marking is carried out according to user fund accounts at counters at two ends of the account marking direction, and when the time length of account marking processing exceeds the preset time or an error code which cannot be confirmed is returned, the account marking state is marked, and an alarm mechanism is triggered; when the account marking fails and returns a preset error code, a retry processing mechanism is carried out, the account marking processing is repeatedly carried out for a preset number of times, and when the account marking still fails after retry, the operation of correcting the account and returning to the original account is carried out, the account marking state is recorded, and the fund of the user is ensured to be correct;
module M3.3: when the serial number is stored in the MySQL database and the failure is abnormal, the local disk file is recorded in a file writing mode, and the file is read through the timing script to try to perform warehousing operation again.
7. The security cross-check entry system of claim 6 wherein said module M3,1 comprises: the security verification and the idempotent verification of the account-marking interface are realized through a token and a parameter signature verification mechanism;
the triggering alarm mechanism in the module M3.2 comprises: the prompt of the number of records of the tab page and/or the red point is sent by short messages and mails and is confirmed and processed manually.
8. The security cross-check entry system of claim 6 further comprising: and multiple query conditions are supported to query each stroke of account flow records and account division states in the MySQL database.
9. The security cross-check entry system of claim 6 further comprising: and settling the account-dividing running water at regular time every day to generate a daily statement, comparing and checking the daily running water uploaded to the two counters with the running water in the MySQL database, and generating a bad account record for manual operation and comparison aiming at the data which cannot be compared.
10. The security cross-check entry system of claim 6 further comprising: and performing authority management setting based on the rbac, and endowing different background users with different roles and different operation authorities by an administrator with fine granularity.
CN202011467374.6A 2020-12-14 2020-12-14 Securities account-marking and registering method and system Pending CN112529556A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011467374.6A CN112529556A (en) 2020-12-14 2020-12-14 Securities account-marking and registering method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011467374.6A CN112529556A (en) 2020-12-14 2020-12-14 Securities account-marking and registering method and system

Publications (1)

Publication Number Publication Date
CN112529556A true CN112529556A (en) 2021-03-19

Family

ID=74999584

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011467374.6A Pending CN112529556A (en) 2020-12-14 2020-12-14 Securities account-marking and registering method and system

Country Status (1)

Country Link
CN (1) CN112529556A (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102831515A (en) * 2011-06-17 2012-12-19 苏州工业园区辰烁软件科技有限公司 Method and system for carrying out electronic fund transfer by mobile equipment
CN108492108A (en) * 2018-03-29 2018-09-04 深圳前海微众银行股份有限公司 Across the chain communication means of block chain, system and computer readable storage medium
CN110414962A (en) * 2019-08-02 2019-11-05 东莞市大易产业链服务有限公司 Inter-bank intelligence transfer account method, device, computer equipment and storage medium
CN111461691A (en) * 2020-04-17 2020-07-28 支付宝(杭州)信息技术有限公司 Flow statistical system, method and device based on block chain

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102831515A (en) * 2011-06-17 2012-12-19 苏州工业园区辰烁软件科技有限公司 Method and system for carrying out electronic fund transfer by mobile equipment
CN108492108A (en) * 2018-03-29 2018-09-04 深圳前海微众银行股份有限公司 Across the chain communication means of block chain, system and computer readable storage medium
CN110414962A (en) * 2019-08-02 2019-11-05 东莞市大易产业链服务有限公司 Inter-bank intelligence transfer account method, device, computer equipment and storage medium
CN111461691A (en) * 2020-04-17 2020-07-28 支付宝(杭州)信息技术有限公司 Flow statistical system, method and device based on block chain

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
史光伟;黄伟;王康贵;王永峰;徐鹏;: "一线通平台的设计与应用", 软件产业与工程, no. 03, pages 39 - 43 *

Similar Documents

Publication Publication Date Title
EP2541413A1 (en) Systems and Methods for Data Integrity Checking
CN108932663B (en) Method and device for simulating matched transaction
CN101918922A (en) Systems and methods for automated data anomaly correction in a computer network
CN112527534A (en) Service processing method, device, equipment and storage medium based on message queue
CN107844575B (en) Personal data sharing system and method for Internet financial platform
US20200234375A1 (en) Protecting against data loss
US11640587B2 (en) Vehicle repair workflow automation with OEM repair procedure verification
CN111027984A (en) Business order processing method and system, electronic equipment and computer storage medium
CN115409590A (en) Unified account checking method, device, equipment and storage medium
CN113312649A (en) Message processing method, device, equipment, system and storage medium
US20170372314A1 (en) Processing of dispute alerts
CN113064759A (en) Block chain data rollback processing method and processing system thereof
US11106811B2 (en) Object storage for guaranteed content for backup and retention
CN103440460A (en) Application system change validation method and system
CN114445079A (en) Document processing method, device, equipment and storage medium
CN112529556A (en) Securities account-marking and registering method and system
US20100312675A1 (en) Systems and Methods for Reporting Chargebacks
CN112116306A (en) Medical reconciliation method based on T +0/N combination
CN111539725A (en) Error data processing method, device and system
US11385953B2 (en) Event activated error resolution
CN113254520B (en) Method for processing credit investigation data missing report and automatically generating supplementary message
CN117314445A (en) Data processing method, device, computer equipment and storage medium for failure transaction
TWM655247U (en) Case Closure Information Collection System
CN113506101A (en) Settlement request, response and cross-platform settlement method, apparatus and medium
CN116226144A (en) Data processing method and device, computer readable storage medium and electronic equipment

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