CN114785875A - Message processing method and system - Google Patents
Message processing method and system Download PDFInfo
- Publication number
- CN114785875A CN114785875A CN202210348155.9A CN202210348155A CN114785875A CN 114785875 A CN114785875 A CN 114785875A CN 202210348155 A CN202210348155 A CN 202210348155A CN 114785875 A CN114785875 A CN 114785875A
- Authority
- CN
- China
- Prior art keywords
- message
- instruction
- request
- state
- revocation
- 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.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 15
- 238000012545 processing Methods 0.000 claims abstract description 97
- 238000012546 transfer Methods 0.000 claims description 6
- 238000000034 method Methods 0.000 abstract description 16
- 230000008569 process Effects 0.000 description 9
- 230000008520 organization Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 241001672694 Citrus reticulata Species 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 238000004080 punching Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000002474 experimental method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/085—Payment architectures involving remote charge determination or related payment systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Computer Security & Cryptography (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention relates to a message processing method and a system, wherein the method comprises the following steps: receiving a first message, and acquiring the type of the first message, wherein the type comprises a request message and a cancel message; if the type of the first message is a revocation message, extracting a revocation instruction detail table from the revocation message, analyzing each revocation instruction in the revocation instruction detail table to perform corresponding processing, and generating processing feedback information; if the type of the first message is a request message, extracting a request instruction detail table from the request message, and marking all request instructions in the request instruction detail table as unprocessed states; circularly reading and analyzing each request instruction in the request instruction list to perform corresponding processing, and generating processing feedback information; generating reply information based on the processing feedback information; wherein the undo instruction is associated with a request instruction. Compared with the prior art, the invention has the advantages of improving the efficiency and the like.
Description
Technical Field
The invention belongs to the technical field of financial data processing, and particularly relates to a message processing method and system.
Background
With the progress of global economy, the exchange of funds among countries around the world frequently occurs. In order to provide high-quality and quick global remittance service for customers, various banks join financial settlement network organizations in a dispute, transmit fund remittance information through a special network, and the whole financial information special transmission network is connected with IT processing systems of various banks to form a global financial information special network for financial information transmission. The Society of Society For world bank Financial Telecommunication (SWIFT For short) is a non-profit international cooperation organization between international banks and industries, where SWIFT operates a world-level Financial text network, and banks and other Financial institutions exchange text with the same industries to complete Financial transactions.
The financial remittance message generally includes remitter bank, remittance receiver bank information, remittance currency, remittance amount and other information, remitter and receiver information and the like. Since the country of the sender and the recipient are different, there are often cases where money exchange is required, that is, money for remittance is exchanged into local money by foreign exchange transaction at the bank where the recipient is located. Because the remittance business relates to banks of a sender and a receiver, the financial settlement message information needs a certain time for transmission on the network, and the process needs a certain manual judgment and processing, thereby affecting the efficiency.
Disclosure of Invention
The present invention aims to overcome the defects in the prior art and provide a method and a system for processing a message with high efficiency.
The purpose of the invention can be realized by the following technical scheme:
a message processing method comprises the following steps:
receiving a first message, and acquiring the type of the first message, wherein the type comprises a request message and a cancel message;
if the type of the first message is a revocation message, extracting a revocation instruction detail table from the revocation message, analyzing each revocation instruction in the revocation instruction detail table to perform corresponding processing, and generating processing feedback information;
if the type of the first message is a request message, extracting a request instruction detail table from the request message, and marking all request instructions in the request instruction detail table as unprocessed states;
circularly reading and analyzing each request instruction in the request instruction list to perform corresponding processing, and generating processing feedback information;
generating reply information based on the processing feedback information;
wherein the undo instruction is associated with a request instruction.
Further, the request message comprises a transfer request message and a direct debit request message.
Furthermore, the content of the request message comprises a file header part and an instruction part, wherein the file header part comprises a message ID, an enterprise BIC and a reserved execution date, the instruction part comprises at least one request instruction, and each instruction has a unique instruction ID;
the content of the revocation message comprises a file header part and an instruction part, wherein the file header part comprises a message ID, an enterprise BIC and a reserved execution date, and the instruction part only comprises a revocation instruction.
Further, analyzing each cancellation instruction in the cancellation instruction list to perform corresponding processing specifically includes:
obtaining a cancel instruction, searching whether a request instruction corresponding to the cancel instruction exists, if so, obtaining the state of the request instruction, correspondingly updating the state of the cancel instruction according to the state of the request instruction, generating processing feedback information, and if not, exiting.
Further, the updating the state of the cancel instruction according to the state of the request instruction specifically includes:
if the request command is in a successful state, carrying out conflict processing, updating the request command in a successful state, and updating the cancel command in a processed state;
if the status of the request instruction is that the account entry fails or the cancellation is cancelled, updating the status of the cancellation instruction to be processed;
if the state of the request instruction is unprocessed, the state of the update request instruction is cancelled, and meanwhile, the state of the update cancellation instruction is processed.
Further, the corresponding processing of each request instruction specifically includes:
and acquiring a request instruction with unprocessed state and reserved execution date, searching whether a cancel instruction with the request instruction exists, if so, updating the state of the request instruction to be cancelled, if not, performing posting processing, and updating the state of the request instruction to be successful or unsuccessful according to a processing result.
Furthermore, the association between the revocation instruction and the request instruction is realized through the message ID, the instruction ID and the enterprise BIC.
The invention also provides a message processing system, comprising:
the message receiving module is used for receiving a first message and acquiring the type of the first message, wherein the type comprises a request message and a cancel message;
the revocation processing module is used for responding when the type of the first message is a revocation message, extracting a revocation instruction detail table from the revocation message, analyzing each revocation instruction in the revocation instruction detail table to perform corresponding processing, and generating processing feedback information;
the request processing module is used for responding when the type of the first message is a request message, extracting a request instruction detail table from the request message, and marking all request instructions in the request instruction detail table into an unprocessed state;
the request instruction processing module is in a continuous operation state, circularly reads and analyzes each request instruction in the request instruction list to perform corresponding processing, and generates processing feedback information;
the reply module generates reply information based on the processing feedback information;
wherein the undo instruction is associated with a request instruction.
Further, the reply module includes:
the revocation reply unit responds to the obtained state update of the revocation instruction and is used for sending the latest state of the revocation instruction;
and the request reply unit responds after acquiring the state update of the request instruction and is used for sending the latest state of the request instruction.
The present invention also provides a computer readable storage medium comprising one or more programs for execution by one or more processors of an electronic device, the one or more programs including instructions for performing the message processing method as described above.
Compared with the prior art, the invention has the following beneficial effects:
the invention designs the automatic processing flow of the request message and the cancellation message, automatically executes corresponding processing according to different states of the instruction, and the request instruction processing module is in a continuous operation state, can process each instruction in time, effectively improves the efficiency of payment, cancellation or correction, is convenient and quick, and does not need to be in a cabinet for an enterprise.
Drawings
FIG. 1 is a schematic flow chart of the present invention.
Detailed Description
The invention is described in detail below with reference to the figures and the specific embodiments. The present embodiment is implemented on the premise of the technical solution of the present invention, and a detailed implementation manner and a specific operation process are given, but the scope of the present invention is not limited to the following embodiments.
As shown in fig. 1, the present invention provides a message processing method, which includes the following steps:
receiving a first message, and acquiring the type of the first message, wherein the type comprises a request message and a cancel message;
if the type of the first message is a revocation message, extracting a revocation instruction detail table from the revocation message, analyzing each revocation instruction in the revocation instruction detail table to perform corresponding processing, and generating processing feedback information;
if the type of the first message is a request message, extracting a request instruction detail table from the request message, and marking all request instructions in the request instruction detail table as unprocessed states;
circularly reading and analyzing each request instruction in the request instruction list to perform corresponding processing, and generating processing feedback information;
and generating reply information based on the processing feedback information.
The content of the request message comprises a file head part and an instruction part, wherein the file head part comprises a message ID, an enterprise BIC and a reserved execution date, the instruction part comprises at least one request instruction, and each instruction has a unique instruction ID; the content of the revocation message comprises a file header part and an instruction part, wherein the file header part comprises a message ID, an enterprise BIC and a reserved execution date, and the instruction part only comprises a revocation instruction. The association between the cancel command and the request command is realized through the message ID, the command ID and the enterprise BIC.
The request message which can be processed by the method comprises a transfer request message and a direct debit request message. The method can process each instruction in time, effectively improves the efficiency of payment, cancellation or correction, is convenient and quick, and does not need to face a cabinet for an enterprise.
The above method, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.
In another specific embodiment, the above processing procedure can be implemented by a message processing system, where the message processing system includes a message receiving module, a revocation processing module, a request instruction processing module, and a reply module, where:
the message receiving module is used for receiving a first message and acquiring the type of the first message, wherein the type comprises a request message and a cancel message;
the revocation processing module responds when the type of the first message is a revocation message, extracts a revocation instruction detail table from the revocation message, analyzes each revocation instruction in the revocation instruction detail table to perform corresponding processing, and generates processing feedback information;
the request processing module responds when the type of the first message is a request message, extracts a request instruction detail table from the request message and marks all request instructions in the request instruction detail table in an unprocessed state;
the request instruction processing module is in a continuous operation state, circularly reads and analyzes each request instruction in the request instruction list to perform corresponding processing, and generates processing feedback information;
the reply module generates reply information based on the processing feedback information, and comprises: the revocation reply unit responds to the obtained state update of the revocation instruction and is used for sending the latest state of the revocation instruction; and the request reply unit responds after acquiring the updated state of the request instruction and is used for sending the latest state of the request instruction.
Example 1
The embodiment is based on a message processing system to perform online processing on the transfer request message.
Interpretation of terms
SWIFT network: the Society For international banking and Telecommunication systems (Society For world across Financial Telecommunication s.c., abbreviated as SWIFT) is a non-profit international cooperation organization between international banking industries. SWIFT operates a world-wide financial electronic text network through which banks and other financial institutions exchange electronic text with businesses to complete financial transactions.
MT 101: the transfer request message is typically sent by the enterprise to an account opening bank or agent bank to remit money to the payee designated in the message. One MT101 message may contain multiple transaction requests.
MT 192: the cancel request message is initiated by the original packet side, and the patent refers to the associated MT101 message initiator. After the enterprise sends MT101, if a payment request (singles) needs to be revoked, MT192 may be sent to instruct the bank to revoke the transaction.
MT 199: and for the state reply messages of the MT101 payment instructions, each MT199 message corresponds to one MT101 payment instruction and is generated and sent by the bank terminal.
MT 196: and generating and sending a response message for withdrawing the message by the MT192 by the bank end.
Punching: if the bank receives the MT101 message, the payment request has been processed, i.e., posted. The bank does the reverse transaction and the amount of the deposit is returned to the payment account.
And (3) BIC: the SWIFT bank identification codes are used for each unit applying for adding SWIFT organization to work out SWIFT address codes of the line in advance according to the unified rule of the SWIFT organization, and the SWIFT bank identification codes take effect formally after being approved by the SWIFT organization.
The usage scenario of the message processing system in this embodiment is as follows: after the enterprise sends the MT101 payment request through the SWIFT network, if the related MT192 message can be sent to the bank to be cancelled, the bank associates the original MT101 payment request according to the MT192 message 21 and the MT192 message 79, and cancels (before entering account) and corrects (enters account) according to the current processing condition. If the MT101 instruction state changes, the bank returns an MT199 state message to the enterprise in time. After the MT192 receives or processes the message, the bank returns an MT196 response message to the enterprise in time. The system can cancel or correct the payment instruction under a plurality of scenes such as the condition that the MT101 arrives at the MT192 first and then arrives, the condition that the MT192 arrives at the MT101 first and then arrives, the MT101 instruction is already checked, the MT101 instruction is not checked and the like. And according to the change of the MT101 payment instruction state, an MT199 state message is returned to the enterprise in real time; and informs the enterprise of the message revocation status after receiving or processing the MT192 message.
MT101 samples are as follows:
in this embodiment, the MT101 includes a message header and message details, where the field 20 of the message header is the ID number of the message, and each message is different. The message detail 21 is a payment ID number, and each payment instruction is different. In the example, the message has 2 fields and 21 fields, namely, two payment instructions are provided.
The header part content is as follows:
20 fields-message ID-0000013043
28 fields-message n package/total package number (for sub-package, sample only 1 package, so 1/1)
50 fields-Payment Account 100200700213638 and Payment name
52 Do-Payment Bank BIC-BKCHHDEBJ 44W
30 fields-reserved execution date 190401, namely 2019, 4 months and 1 day
Payment order 1:
21 The Payment order ID-0000013485
32 field-payment amount $ 13.02
57 field-collection line BIC-BKCHHDEFF
59 field-Account number 100200700215206 and name
71A: charge undertaking mode-shared undertaking by collection and payment person
Payment instruction 2:
21 The Payment order ID-0000013486
32-Payment amount 14 yen
57 field-collection line BIC-BKCHCNCBJ
59 Lot-Account number 100200700218412 and name
71A: fee undertake mode-shared undertake by the payee
MT192 samples are as follows:
the message 20 field is the ID number of the message, and each message is different. The 21 fields are 20 fields of the associated MT101 message. 11S the first and second lines are the 30 fields of the associated message type 101 and 101 messages, respectively, the appointment date. The field 79 is the message detail 21 field of the associated MT101, and each MT192 message can only withdraw a payment request.
20 fields-message ID-0000013765
21 field-associated MT101 message ID0000013043
11S first line: the associated message type is 101
11S second line: the 30 fields of the associated MT101 message are 190401 (i.e. 4 months and 1 day in 2019)
79 field: associated MT101 payment instruction ID0000013485
MT199 samples were as follows:
the message header 20 field is the ID number of the message, and each message is different. 21 fields of the 21-field original MT101 message. 79 status of initial behavior (ACSC-checked, RJCT-not checked, ACCR-cancel request processed, i.e. not checked), and description of subsequent behavior processing.
MT196 samples are as follows:
the message header 20 field is the ID number of the message, and each message is different. 21 fields of the MT192 message. 76 fields are state descriptions (RCVD-received, ACCP-processed).
In this embodiment, the specific functions of each module of the message processing system are as follows:
and the message receiving module S0 splits the message type from the message fixing position after receiving the message. In particular embodiments, this may be determined from the bold text portion 101 or 192 and the sender, business bic (creatchzf). And respectively calling a revocation processing module S1 or a request processing module S2 according to the message types.
The cancel processing module S1 splits 21/11/79 fields and records the instruction list (state RCVD) of MT 192. And according to 21 fields, 11S fields and enterprise BIC and 79 fields in the instruction, the corresponding MT101 instruction is searched from the MT101 instruction list. If the MT101 state is found to be successfully posted (ACSC), a background positive charge transaction is called, the MT101 instruction is updated to be successfully charged (ACCR), and the MT192 state is processed (ACCP); if found and the status is failed crediting (RJCT) or revoked (ACSC), updating the MT192 status to processed (ACCP); if found and the status is unprocessed, updating the MT101 instruction status as revoked (ACCR) and the MT192 status as processed (ACCP); if not found, exit. If the MT101 instruction state changes, the request reply unit S4 needs to be invoked; the MT192 receives or has processed the withdrawal message and invokes the withdrawal reply unit S5.
The request processing module S2 splits the file header and the file details, and records the instruction detail table of the MT101, where the state of the split details is to be processed.
The request instruction processing module S3, which is a resident daemon. The process circularly reads all the MT101 payment instructions with unprocessed states and system dates < ═ message 30 fields, namely the reserved dates are reached from the MT101 instruction detail table, and searches the corresponding 192 instructions from the MT192 instruction detail table according to 20 fields, 21 fields, 30 fields and enterprise BIC in the instructions. If so, updating the instruction state of the MT101 to be cancelled (ACCR), and updating the instruction state of the MT192 to be processed (ACCP); if not, calling a corresponding accounting interface to perform accounting processing, and setting the MT101 instruction state as success (ACSC) or failure (RJCT) according to the background return state. If the MT101 instruction state changes, the request reply unit S4 needs to be invoked; the MT192 is processed and calls the revocation reply unit S5.
The request reply unit S4 generates 199 a message according to the updated state ACCR, ACSC or RJCT of the MT101, and sends the message to the enterprise.
The cancellation reply unit S5 generates 196 a message according to the updated states RCVD and ACCP of the MT192, and sends the message to the enterprise.
Example 2
The embodiment is based on a message processing system to perform online processing on a direct debit request message.
Interpretation of terms
The MT 104: and directly debiting the request message. One MT104 message may contain multiple collect instructions.
Sent by the enterprise to the bank via the SWIFT network, where the bank pays money directly from the payer's account according to the contract (agreement) and transfers it to the enterprise's collection account. The payment account may be a receiving bank home bank account or an account of an other bank. Enterprises need to sign a commission agreement with banks.
MT 192: the cancel request message is initiated by the original packet side, which refers to the associated MT104 message initiator. After the enterprise sends the MT104, if a receipt request (single) needs to be cancelled, the MT192 may be sent to instruct the bank to cancel the transaction.
MT 199: and for the state reply messages of the MT104 collection instructions, each MT199 message corresponds to one MT104 collection instruction and is generated and sent by the bank end.
MT 196: and generating and sending a response message for withdrawing the message by the MT192 by the bank end.
Punching: if the bank receives the MT104 message, the collection request is processed, i.e., posted. The bank does the reverse transaction and the amount of the deposit is returned to the payment account.
The usage scenario of the message processing system of the embodiment is as follows: after the enterprise sends the MT104 direct debit (collection) request through the SWIFT network, if the related MT192 message can be cancelled to the bank, the bank correlates to the original MT104 collection request according to the MT192 message 21 field, and cancels (before entering account) and corrects (after entering account) according to the current processing condition. If the MT104 instruction state changes, the bank returns an MT199 state message to the enterprise in time. After the MT192 receives or processes the message, the bank returns an MT196 response message to the enterprise in time. The system can cancel or correct the collection instructions under a plurality of scenes such as that the MT104 arrives at the MT192 first and then arrives, that the MT192 arrives at the MT104 first and then arrives, that the MT104 instruction is checked in, that the MT104 instruction is not checked in and the like. And returns MT199 status messages to enterprises in real time according to the change of MT104 collection instruction status; and informs the enterprise of the message revocation status after receiving or processing the MT192 message.
MT104 sample is as follows:
in this embodiment, the MT104 includes a message header and message details, where the field 20 of the message header is the ID number of the message, and each message is different. The message detail 21 is a collection ID number, and each collection instruction is different. In the sample, 2 messages are sent for 21 fields, namely, two collection instructions are provided.
The header part content is as follows:
20 field-message ID T300164800
30 fields-reserved execution date 190401, namely 2019, 4 months and 1 day
50 fields-Account of receipt 325956086490 and name of receipt
52-Cash line number-104100000045 and name
Collection instruction 1:
21 field-collection instruction ID-T300164801
32 field-collection amount 2.00 RMB
57 Fair-Payment line number 105301000013
59 field-Payment Account 778350120134 and name
70 field: mandarin Chinese character of' annex
A charging instruction 2:
21 field-collection instruction ID-T300164802
32 field-collection amount 60000 RMB
57 Fair-Payment line number 105301000013
59 field-Payment Account 778350120178 and name
70 field: mandarin Chinese character of' annex
MT192 samples are as follows:
the message 20 field is the ID number of the message, and each message is different. The 21 fields are 20 fields of the associated MT104 message. The first and second lines of 11S are the 30 fields, i.e. appointment dates, of the associated message type 104 and 104 messages, respectively. 79 fields are associated with MT104 message details 21 fields, and each MT192 message can only withdraw a collection request.
20 fields-message ID0000013765
21 field-associated MT104 collect message ID-T300164800
11S first line: the associated message type is 104
11S second line: the 30 fields of the associated MT104 message are 190401 (i.e. 4 months and 1 day in 2019)
79 field: associated MT104 collection instruction ID-T300164801
MT199 samples were as follows:
the message header 20 field is the ID number of the message, and each message is different. 21 fields of the 21-field original MT104 message. 79 status of initial behavior (ACSC-checked, RJCT-not checked, ACCR-cancel request processed, i.e. not checked), and description of subsequent behavior processing.
MT196 samples are as follows:
the message header 20 field is the ID number of the message, and each message is different. 21 fields of the MT192 message. 76 fields are state descriptions (RCVD-received, ACCP-processed).
In this embodiment, the specific functions of each module of the message processing system are as follows:
and the message receiving module S0 splits the message type from the message fixed position after receiving the message (the bold part 104 or 192 of the text box and the sending party, namely the enterprise BIC (CRESCHZF)), and calls the revocation processing module S1 or the request processing module S2 according to the message type.
The cancel processing module S1 splits 21/11/79 fields and records the instruction list (state RCVD) of MT 192. And the corresponding MT104 instruction is looked up from the MT104 instruction list according to 21 fields, 11S and enterprise BIC and 79 fields in the instruction. If the MT104 state is found to be successfully posted (ACSC), a background positive charge transaction is called, the MT104 instruction is updated to be successfully charged (ACCR), and the MT192 state is processed (ACCP); if found and the status is failed crediting (RJCT) or revoked (ACSC), updating the MT192 status to processed (ACCP); if found and the status is unprocessed, the MT104 instruction status is updated to be revoked (ACCR), and the MT192 status is processed (ACCP); if not found, exit. If the MT104 command state changes, the request reply unit S4 needs to be invoked; the MT192 receives or has processed the withdrawal message and invokes the withdrawal reply unit S5.
The request processing module S2 splits the file header and the file detail, and records the instruction detail table of the MT104, where the state of the split detail is to be processed.
And requesting an instruction processing module S3, wherein the module is a resident daemon process. The process circularly reads all the MT104 payment instructions with the states of unprocessed and the system date < ═ message 30 fields, namely the MT104 payment instructions with the appointed dates, from the MT104 instruction detail table, and searches the corresponding 192 instructions from the MT192 instruction detail table according to 20 fields, 21 fields, 30 fields and enterprise BIC in the instructions. If so, updating the MT104 instruction state to withdrawn (ACCR) and the MT192 instruction state to processed (ACCP); if not, calling a corresponding accounting interface to perform posting processing, and setting the MT104 instruction state as success (ACSC) or failure (RJCT) according to the background return state. If the MT104 command state changes, the request reply unit S4 needs to be invoked; the MT192 is processed and calls the revocation reply unit S5.
The request reply unit S4 generates 199 a message according to the updated state ACCR, ACSC or RJCT of the MT104, and sends the message to the enterprise.
The cancellation reply unit S5 generates 196 a message according to the updated states RCVD and ACCP of the MT192, and sends the message to the enterprise.
The foregoing detailed description of the preferred embodiments of the invention has been presented. It should be understood that numerous modifications and variations could be devised by those skilled in the art in light of the present teachings without departing from the inventive concepts. Therefore, the technical solutions that can be obtained by a person skilled in the art through logical analysis, reasoning or limited experiments based on the prior art according to the concepts of the present invention should be within the scope of protection determined by the claims.
Claims (10)
1. A message processing method is characterized by comprising the following steps:
receiving a first message, and acquiring the type of the first message, wherein the type comprises a request message and a cancel message;
if the type of the first message is a revocation message, extracting a revocation instruction detail table from the revocation message, analyzing each revocation instruction in the revocation instruction detail table to perform corresponding processing, and generating processing feedback information;
if the type of the first message is a request message, extracting a request instruction detail table from the request message, and marking all request instructions in the request instruction detail table as unprocessed states;
circularly reading and analyzing each request instruction in the request instruction list to perform corresponding processing, and generating processing feedback information;
generating reply information based on the processing feedback information;
wherein the undo instruction is associated with a request instruction.
2. The message processing method of claim 1, wherein the request message includes a transfer request message and a direct debit request message.
3. The message processing method according to claim 1, wherein the content of the request message comprises a header part and an instruction part, the header part comprises a message ID, an enterprise BIC and a reserved execution date, the instruction part comprises at least one request instruction, and each instruction has a unique instruction ID;
the content of the revocation message comprises a file header part and an instruction part, wherein the file header part comprises a message ID, an enterprise BIC and a reserved execution date, and the instruction part only comprises a revocation instruction.
4. The message processing method according to claim 1, wherein analyzing each cancellation instruction in the cancellation instruction list to perform corresponding processing specifically comprises:
obtaining a cancel instruction, searching whether a request instruction of the cancel instruction exists, if so, obtaining the state of the request instruction, correspondingly updating the state of the cancel instruction according to the state of the request instruction, generating processing feedback information, and if not, exiting.
5. The message processing method according to claim 4, wherein the updating the state of the cancel instruction according to the state of the request instruction specifically includes:
if the request command is in a successful state, carrying out conflict processing, updating the request command in a successful state, and updating the cancel command in a processed state;
if the state of the request instruction is that the account entry fails or the cancel instruction is cancelled, updating the state of the cancel instruction to be processed;
if the state of the request instruction is unprocessed, the state of the update request instruction is cancelled, and the state of the update cancellation instruction is processed.
6. The message processing method according to claim 3, wherein the corresponding processing for each request instruction specifically comprises:
and acquiring a request instruction with unprocessed state and reserved execution date, searching whether a cancel instruction with the request instruction exists, if so, updating the state of the request instruction to be cancelled, if not, performing posting processing, and updating the state of the request instruction to be successful or unsuccessful according to a processing result.
7. The message processing method of claim 3 wherein the association of the withdraw command with the request command is achieved by a message ID, a command ID, and an enterprise BIC.
8. A message processing system, comprising:
the message receiving module is used for receiving a first message and acquiring the type of the first message, wherein the type comprises a request message and a cancellation message;
the revocation processing module is used for responding when the type of the first message is a revocation message, extracting a revocation instruction detail table from the revocation message, analyzing each revocation instruction in the revocation instruction detail table for corresponding processing, and generating processing feedback information;
the request processing module is used for responding when the type of the first message is a request message, extracting a request instruction detail table from the request message, and marking all request instructions in the request instruction detail table into an unprocessed state;
the request instruction processing module is in a continuous operation state, circularly reads and analyzes each request instruction in the request instruction list to perform corresponding processing, and generates processing feedback information;
the reply module generates reply information based on the processing feedback information;
wherein the undo instruction is associated with a request instruction.
9. The message processing system of claim 8, wherein the reply module comprises:
the revocation reply unit is used for responding after acquiring the state update of the revocation instruction and sending the latest state of the revocation instruction;
and the request reply unit responds after acquiring the updated state of the request instruction and is used for sending the latest state of the request instruction.
10. A computer-readable storage medium comprising one or more programs for execution by one or more processors of an electronic device, the one or more programs including instructions for performing the message processing method of any of claims 1-7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210348155.9A CN114785875B (en) | 2022-03-29 | 2022-03-29 | Message processing method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210348155.9A CN114785875B (en) | 2022-03-29 | 2022-03-29 | Message processing method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN114785875A true CN114785875A (en) | 2022-07-22 |
CN114785875B CN114785875B (en) | 2024-02-23 |
Family
ID=82427424
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210348155.9A Active CN114785875B (en) | 2022-03-29 | 2022-03-29 | Message processing method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114785875B (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101916421A (en) * | 2010-09-01 | 2010-12-15 | 中国建设银行股份有限公司 | Foreign exchange remittance service processing method and system |
WO2016112675A1 (en) * | 2015-01-12 | 2016-07-21 | 广州广电运通金融电子股份有限公司 | Financial self-service system processing method |
CN110519271A (en) * | 2019-08-28 | 2019-11-29 | 中国银行股份有限公司 | It can support the SWIFT message processing method and system of file transmission by all kinds of means |
CN110896413A (en) * | 2019-11-18 | 2020-03-20 | 中国银行股份有限公司 | Message processing method and device |
CN110910106A (en) * | 2019-11-29 | 2020-03-24 | 中国银行股份有限公司 | Cash management message processing method and system |
-
2022
- 2022-03-29 CN CN202210348155.9A patent/CN114785875B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101916421A (en) * | 2010-09-01 | 2010-12-15 | 中国建设银行股份有限公司 | Foreign exchange remittance service processing method and system |
WO2016112675A1 (en) * | 2015-01-12 | 2016-07-21 | 广州广电运通金融电子股份有限公司 | Financial self-service system processing method |
CN110519271A (en) * | 2019-08-28 | 2019-11-29 | 中国银行股份有限公司 | It can support the SWIFT message processing method and system of file transmission by all kinds of means |
CN110896413A (en) * | 2019-11-18 | 2020-03-20 | 中国银行股份有限公司 | Message processing method and device |
CN110910106A (en) * | 2019-11-29 | 2020-03-24 | 中国银行股份有限公司 | Cash management message processing method and system |
Also Published As
Publication number | Publication date |
---|---|
CN114785875B (en) | 2024-02-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107103462B (en) | Method and device for processing snapshot data of cross-border remittance of bank | |
CN107123038B (en) | Accounting data processing method and device | |
RU2013113167A (en) | SYSTEMS AND METHODS FOR PAYING ACCOUNTS FOR PAYING CUSTOMERS USING THE PAYMENT PLATFORM OF THE SUPPLIER BILLING THE PAYMENT BILL | |
CN109359964A (en) | The real-time account checking method of multi-party payment channel | |
CN101877101A (en) | Bank payment system and operating method thereof | |
CN112508570A (en) | Supply chain financial system based on block chain | |
CN111047310A (en) | Method and device for realizing distribution and transfer of digital assets and online financing | |
CN108762895B (en) | Method and device for processing distributed transaction | |
CN113554509B (en) | Processing method, device, medium and electronic equipment for online payment service | |
CN113657846A (en) | Enterprise fund management method and system in financial sharing mode | |
JP6187947B1 (en) | Multi-bank pooling system and multi-bank pooling method | |
CN115147202B (en) | Banking account processing system, method and device | |
US20070067238A1 (en) | System and method for transferring information between financial accounts | |
CN114785875A (en) | Message processing method and system | |
CN113168650A (en) | Method for automatic transfer between banks and system for implementing same | |
US20230394449A1 (en) | Method and system for transferring funds between accounts | |
CN114971637A (en) | Risk early warning method, device, equipment and medium | |
CN114493817A (en) | Accounting processing method and device, electronic equipment and storage medium | |
CN113822670A (en) | Payment message conversion method and device and electronic equipment | |
CN113034125A (en) | Transaction account separating method and system | |
CN117437076B (en) | Account checking method, device, equipment and medium based on account checking code | |
CN111951002B (en) | Automatic merchant credit giving system for one-card recharging | |
JP2797969B2 (en) | Foreign money transfer business automatic processing device and method | |
JP7305907B2 (en) | Server, method and program in customer information management system of financial institution | |
CN114936184A (en) | Bank-enterprise interconnection transaction method, device, system and 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 |