JP6212026B2 - Payment result notification system and method - Google Patents

Description

  The present invention relates to a deposit result notification system and method.

  International remittances (hereinafter referred to as “overseas remittances”) from domestic financial institution accounts to overseas financial institution accounts use the SWIFT network provided by the Society for Worldwide Interbank Financial Telecommunication (SWIFT). Is done by. Specifically, the amount debited from the sender's account via the SWIFT network using a financial institution identification code (SWIFT BIC: Bank Identifier Cord; hereinafter simply referred to as SWIFT code) registered with the association. However, remittance processing is performed between domestic and overseas financial institutions, and the money is finally credited to the recipient's account.

  As international exchanges become more active, opportunities for overseas remittances have increased. For this reason, overseas remittance methods have been proposed in order to increase efficiency and convenience for customers. For example, in Patent Document 1, when a domestic business server receives remittance information including a remittance destination and remittance amount from the sender's mobile phone terminal, the overseas business server confirms the existence of the remittance destination and exchange rate. Describes an overseas remittance system that calculates a deposit amount based on the above, requests a deposit to a deposit-dedicated account, and transmits an overseas remittance message to an overseas operator server.

  The domestic financial institution server described in the above-mentioned Patent Document 1 executes the batch remittance processing for the business account held by the overseas communication carrier when the time of the collective remittance arrives. , The recipient's mobile phone terminal is contacted to pay the remittance amount.

JP 2011-095920 A

  According to the overseas remittance system described in the above-mentioned Patent Document 1, the overseas business server can surely perform remittance by confirming the existence of the contact information of the overseas remittance after accepting the overseas remittance request. It becomes possible.

  However, the party who made the overseas remittance can receive the remittance processing notification, but not the completion of the deposit processing for the other party. For this reason, it is not known whether or not the side receiving the funds (remittance destination) has received the money. This is because a mechanism for returning the result in response to a remittance request is not defined as a standard in SWIFT.

  The present invention has been made in view of such a situation, and provides a payment result notification system and method that can confirm whether or not the side of the remittance has securely received money on the other side. Objective.

  In order to solve the above problems, the deposit result notification system of the present invention provides the following solution.

A destination-side remittance server that is connected to the SWIFT network and generates a remittance message based on a remittance request from a destination-side customer's terminal; the destination-side remittance server; and the SWIFT network that is connected to the destination-side remittance server Based on the remittance message from the destination, the destination remittance server for depositing the payee account, and when the deposit processing to the payee account is completed, the destination remittance server and the destination side The remittance server is connected to a network different from the SWIFT network, the remittance message is received from the destination remittance server, and the deposit to the payee account based on the remittance request is completed. A data linkage server that transmits a payment processing completion notification indicating that the remittance message has been generated to the destination-side remittance server that has generated the remittance message. Server, if the flag that specifies whether the transfer to perform payment result notification is set in the transfer message, by referring to Reference number of the deposit process completion notification, extracts remittance information relevant , Reflecting the payment processing completion notification in the remittance information, storing the payment result data in the remittance message DB in which the remittance information for each customer is registered, and reflecting it in the system in which the remittance information for each customer is managed The payment result notification is notified to the terminal of the destination customer.

  The data linkage server may be connected as a hub to a destination-side and destination-side remittance server in a plurality of countries or regions.

According to another aspect of the present invention, there is provided a processing method for notifying a deposit result in a deposit result notification system comprising a destination-side remittance server, a destination-side remittance server, and a data linkage server, the SWIFT network The remittance server connected to the destination generates a remittance message based on a remittance request from a terminal on the customer's destination side, and the destination side connected to the remittance server on the destination side and the SWIFT network The remittance server, based on the remittance message from the destination remittance server, the step of depositing into the payee account, and when the data linkage server has completed the deposit processing to the payee account, The destination-side remittance server and the destination-side remittance server are connected to the destination-side remittance by a network different from the SWIFT network. A payment processing completion notification indicating that payment to the recipient account based on the remittance request has been completed is sent to the destination remittance server that generated the remittance message. The sending step and the destination remittance server refer to the reference number of the deposit processing completion notification when the flag specifying whether or not the remittance to be notified of the deposit result is set in the remittance message. The remittance information is extracted, the remittance processing completion notification is reflected in the remittance information, the remittance data is stored in the remittance message DB in which the remittance information for each customer is registered, and the remittance for each customer is stored. Performing a step of reflecting in a system in which information is managed, and a step of notifying the payment result notification to a terminal of a customer on the destination side, That.

  ADVANTAGE OF THE INVENTION According to this invention, the payment result notification system and its method which can confirm whether the side which performed remittance paid reliably to the other party can be provided.

It is a figure which shows the image of the payment result notification system which concerns on embodiment of this invention. It is a figure which shows the outline of the payment result notification system which concerns on embodiment of this invention. It is a figure which shows the functional block of the payment result notification system which concerns on embodiment of this invention. (A) is a figure which shows an example of the data structure of remittance message DB. (B) is a figure which shows an example of a data structure of payment result information DB. It is a sequence diagram which shows the processing operation of the payment result notification system which concerns on embodiment of this invention. It is a figure which shows an example of the remittance information display screen on which the payment result was displayed.

  DESCRIPTION OF EMBODIMENTS Hereinafter, a mode for carrying out the present invention (hereinafter referred to as this embodiment) will be described in detail with reference to the accompanying drawings. Note that the same numbers or symbols are assigned to the same elements throughout the description of the embodiment.

  FIG. 1 is an image diagram of a payment result notification system according to the present embodiment. Hereinafter, the above system will be referred to as “the present system”.

  This system provides a relay server (data linkage server) that serves as a hub between the remittance server on the destination side (remittance side) and the remittance server on the destination side (payment side) when performing overseas remittance. And a mechanism for notifying the remittance side that the depositing process to the receiving side has been completed. Hereinafter, the “remittance server” means a server that performs processing (remittance processing and deposit processing) on both the destination side and the destination side in the remittance system of a financial institution.

  When a customer makes an overseas remittance, a method of requesting remittance at a financial institution's window, a method in which a company that can connect to the SWIFT network makes a direct remittance request to the system of the destination financial institution, or using the Web There is a method of requesting remittance using an internet banking system. In the present embodiment, overseas remittance using an internet banking system will be mainly described. In this case, it is assumed that the remittance recipient account of the other party is registered in advance with the financial institution and the procedure for enabling overseas remittance has been completed. In addition, the payment result notification described later provided by this system may be deployed as a service for all customers who perform overseas remittance, but as a service provided only to specific customers with a service usage contract (referred to as premium customers). Also good.

  The customer accesses the destination remittance server by inputting authentication information (login ID, password, etc.) from the information terminal owned by the customer (referred to as the destination terminal) using the Internet banking system. . Next, the customer inputs information necessary for overseas remittance displayed on the screen. In addition, necessary information for overseas remittance (hereinafter sometimes referred to as remittance information) is, for example, pre-registered remittance recipient account information (name of financial institution of the remittance partner, name of remittance partner, account number) ), Remittance name, account number, remittance amount, etc.

  When the remittance server on the destination side receives the necessary information, it checks the account information of the customer who is the remittance (for example, whether the account exists, whether the account number matches the account holder, Whether the account balance is insufficient, etc.) If there is no problem as a result of the check, a remittance message is generated in a standard format of SWIFT (for example, MT103: Message Type 103) based on necessary information, and the generated message is transferred to a remittance message database (hereinafter referred to as remittance message DB and Store). Then, based on the generated remittance message, an AML (Anti-Money Laundering) check for preventing money laundering is performed, and the message is transmitted to the destination remittance server via the SWIFT network.

  When sending payment instructions to the other financial institution using Internet banking, a fixed-format MT103 is generated. However, in the case of a corporation that can be directly connected to SWIFT, the remittance message ( A method of generating MT 101) or a method of sending and receiving structured financial transaction data or a large amount of data called FileAct can be used. A remittance message such as MT101 or MT103 in the SWIFT network is only one way of transmission and cannot receive a reply to the remittance message, but since FileAct can flexibly define the format, a remittance request via the SWIFT network Can also receive a reply. However, in the method using FileAct, it is necessary to define the format uniquely, and both the customer system and the financial institution system need to be customized individually. Have difficulty. Therefore, in this system, the SWIFT standard method is used for the remittance request, but the payment processing completion notification (payment result notification) for the remittance request uses a network of another route that does not go through the SWIFT network. The network of another route may be a network within a financial institution (intra-bank network) or a network between financial institutions (hereinafter, both are collectively referred to as “intra-bank network etc.”).

  Returning to FIG. 1, the remittance server on the receiving side that received the remittance message decodes the received remittance message, performs AML check on the destination side based on the decrypted remittance information, and remittance information included in the remittance message Based on the above, the deposit processing to the customer account of the receiving side which is the remittance destination is executed. In addition, in the overseas remittance, the reason for performing the AML check twice on the destination side and the destination side is that the contents of the AML check differ depending on the country and region.

  When the deposit processing is completed, the destination-side remittance server transmits a deposit processing completion notification to the data linkage server via a network different from the SWIFT network, specifically, an intra-bank network of the financial institution. In response to this, the data linkage server transmits the received payment processing completion notification to the remittance server on the destination side via the intra-bank network or the like.

  When the destination remittance server receives the deposit processing completion notification, the destination remittance server stores the deposit processing completion notification in the database in which the remittance information for each customer is registered, and reflects it in the system in which the remittance information for each message is managed. With the mechanism described above, in the case of overseas remittance, in response to the problem that the sending party did not know whether or not the recipient's deposit process was completed, the payment process completion result was notified to the remittance system, and the result By displaying, the payment to the receiving side can be confirmed from the sending side.

  The data linkage server also plays a role of data linkage between a pooling server that collects and distributes (pools) funds between accounts of a corporate group and a billing server, and a billing server that has balance information of each account. Also, it is configured to perform data linkage with an AML server that performs money laundering check of each transaction and a funding agreement between bases and, in some cases, a market server that executes funding in an external financial market. .

  For example, as shown in FIG. 2, the pooling server can acquire the account balance information of each customer from the account server by cooperating with the data cooperation server. Then, the pooling server calculates a transfer amount of funds according to the transaction from the acquired account balance information, and transmits the result (fund transfer instruction) to the data linkage server. In addition, the AML server and the market server can receive data from the data linkage server, and can perform data linkage of funds transfer associated with pooling. The data linkage server also includes a pooling relay means for collecting and distributing funds within the corporate group, and even in multi-bank pooling that transfers funds by pooling to other accounts within the corporate group (in this case Can be sent to the pooling server. With this mechanism, it becomes possible to notify the processing result of the funds transfer in the transaction within the company group, and the pooling process including other banks can be performed smoothly.

(Configuration of payment result notification system)
FIG. 3 is a functional block diagram of the payment result notification system according to the present embodiment. This system typically includes a destination terminal 10, a domestic financial institution system 30 (destination side) connected to the destination terminal 10 via the Internet 80, a domestic financial institution system 30, and a SWIFT network 60. Overseas financial institution system 40 (destination side) to be connected, destination-side terminal 20 connected to overseas financial institution system 40 via the Internet 80, domestic financial institution system 30, overseas financial institution system 40, and SWIFT network 60 And a data linkage server 50 connected via a different network (in-line network 70, etc.).

  The destination terminal 10 transmits remittance instruction information to the domestic financial institution system 30 based on the remittance request from the requester (remittance instruction). Specifically, the client accesses the domestic financial institution system 30 using the Internet banking system (Internet banking server 32) and inputs information necessary for overseas remittance. Then, the destination terminal 10 takes in information necessary for overseas remittance and transmits necessary information to the domestic financial institution system 30.

(Structure of domestic financial institution system)
The domestic financial institution system 30 typically includes a SWIFT connection communication unit 31, an internet banking server 32, a remittance server 33, a billing server 35, an AML server 36, and a SWIFT notification server 38. .

  The SWIFT connection communication unit 31 transmits a remittance message to the overseas financial institution system 40 corresponding to the SWIFT code based on the SWIFT code.

  The internet banking server 32 provides a service for accessing domestic and overseas remittance procedures by accessing a financial institution with which customers make transactions via the Internet. It also provides services such as user account balance information, transfers, and transfers.

  The remittance server 33 includes a remittance message generator 34 and a remittance message DB 100. The remittance message generator 34 generates a message based on remittance information from the destination side. Specifically, when remittance information for overseas remittance is received from the destination customer terminal (destination side terminal 10), the account server 35 is instructed to check whether the account balance of the destination customer is greater than the remittance amount included in the remittance information. Send. If there is no problem as a result of the check, a remittance message is generated based on the remittance information. Then, an AML check instruction is transmitted to the AML server 36 based on the remittance message. If there is no problem as a result of the AML check, a remittance message is transmitted to the overseas financial institution system 40 of the bank or group through the SWIFT connection communication unit 31.

  In addition, when the remittance server 33 receives a payment result notification indicating that the payment to the payee account based on the remittance request is completed from the data cooperation server 50, the remittance server 33 presents the payment result notification to the destination terminal 10. Details will be described later.

  The remittance message DB 100 stores remittance information for each overseas remittance request of the destination customer. As shown in FIG. 4A, “reception ID” numbered for each request for overseas remittance, “user ID”, “message type”, “AML check” numbered for each user of this service. , “Settlement date”, “Destination financial institution”, “Recipient”, “Account number”, “Currency”, and “Remittance amount” are registered.

  For example, the remittance request with the reception ID “00010” and the user ID “A00123” is generated in the format of the message type “MT103”, the AML check result is “normal”, and the settlement date of the overseas remittance is “2014”. June 26 of the year ". The destination financial institution is “XX Bank London Branch”, the payee is “AAA Corporation”, and the account number is “012-1234567”. Also, it is registered that the remittance amount is “1,000,000” and the currency is “USD”.

  Returning to FIG. 3, the account server 35 is included in the remittance information and the account information database (not shown) received from the remittance server 33, whether the account exists, whether the account number matches the account holder, and the remittance information. Based on the remittance amount, it is checked whether the account balance of the destination customer is equal to or greater than the remittance amount included in the remittance information, and the check result is transmitted to the remittance server 33.

  The AML server 36 includes an AML check unit 37 and a check target message database 200 (hereinafter referred to as a check target message DB).

  The check target message DB 200 stores the remittance message transmitted from the remittance server 33 and stores the check result of the AML check unit 37. Based on a predetermined rule, the AML check unit 37 performs a money laundering check on the remittance message stored in the check target message DB 200, checks whether each remittance message has a problem, and stores the data. Update and send the check result to the remittance server 33.

  The SWIFT notification server 38 is a transaction system other than the Internet banking system, where a corporate system (not shown) that can be directly connected to the SWIFT network generates a direct message (MT101) and transfers money overseas, or using FileAct It plays the role of accepting large amounts of overseas remittances. In this system, even for a remittance request in such a case, the payment result notification can be transmitted using Internet banking.

(Structure of overseas financial institution system)
The overseas financial institution system 40 typically includes a SWIFT connection communication unit 41, an internet banking server 42, a remittance server 43, a billing server 45, an AML server 46, and a SWIFT notification server 48. .

  The SWIFT connection communication unit 41 transmits the remittance message received from the domestic financial institution system 30 via the SWIFT network 60 to the remittance server 43.

  The remittance server 43 includes a remittance message decrypting unit 44 and a remittance message DB 100. The remittance message decrypting unit 44 decrypts the remittance message received from the domestic financial institution system 30, changes it to a predetermined format (remittance information), and transmits it to the accounting server 45.

  Based on the remittance information received from the remittance server 43, the account server 45 executes the deposit processing of the remittance amount specified in the remittance information to the account of the customer on the destination side, and sends the transfer result to the remittance server 43. Send.

  The internet banking server 42 captures the transfer result received through the remittance server 43 and reflects it in a dedicated application for overseas remittance.

  The SWIFT notification server 48 sends a received transfer result to a database (not shown) of the SWIFT notification server 48 via the remittance server 43, the AML server 46, and the accounting server 45 for overseas remittances made by direct transactions. And notify the recipient (corporate, etc.).

  If the destination is a financial institution outside the group, the out-of-group financial institution system 40 ′ is connected to the data linkage server 50 via the gateway 90 and the intra-bank network 70. It is assumed that the non-group financial institution system 40 ′ has the same function as that of the bank or the overseas financial institution system 40 of the own group for notifying the payment result. Otherwise, it is considered that the deposit process has been completed when the remittance is made to the non-group financial institution system 40 '.

(Data linkage server)
The data linkage server 50 is typically composed of a payment result notification unit 51. The data linkage server 50 is connected to remittance servers (33, 34) on the destination side and the destination side in a plurality of countries or regions.

  When the overseas financial institution system 40 (including the non-group financial institution system 40 ′ having the same function. The same applies hereinafter) completes the deposit processing, the payment result notification unit 51 receives the remittance message from the destination remittance server 43. The deposit processing result is received, and a deposit result notification indicating that the deposit to the payee account based on the remittance request is completed is transmitted to the destination remittance server 33. The remittance message and the payment result notification are linked by the reference number assigned by the destination remittance server. In the case of a remittance instruction message at the destination remittance server, for example, MT103, a reference number is set to tag 20 in the format of MT103, and the remittance server (payment side system) at the destination side receives the “original transaction number” in the payment result notification. The reference number of the original message is set in the item and the payment result is transmitted.

  A deposit result information database 300 (hereinafter referred to as a deposit result information DB) that stores the deposit processing status for each overseas remittance request may be provided. In the deposit result information DB 300, for example, as shown in FIG. 4B, items of “reception ID”, “user ID”, “payment process completion date and time”, and “status” indicating the deposit processing status of overseas remittance are included. It is registered. As the status status, “Credited” that has been processed and “Creating” that is creating a message are registered.

  Although omitted in the present description, in both the domestic financial institution system 30 and the overseas financial institution system 40, the destination side and the destination side may naturally be reversed, so both financial institution systems are provided with a common functional block. ing.

  The functional block configuration of the above system is merely an example, and one functional block (database and functional processing unit) may be divided, or a plurality of functional blocks may be configured as one functional block. Good. Each function processing unit reads a computer program stored in a storage device such as a ROM (Read Only Memory), flash memory, SSD (Solid State Drive), or hard disk by a CPU (Central Processing Unit) built in the device This is realized by a computer program executed by the CPU. That is, in each function processing unit, this computer program reads and writes necessary data such as a table from a database (DB; Data Base) stored in a storage device or a storage area on a memory, and may be related in some cases. This is realized by controlling hardware (for example, an input / output device, a display device, and a communication interface device). In addition, the database in the embodiment of the present invention may be a commercial database, but it simply means a collection of tables and files, and the internal structure of the database itself does not matter.

(Processing operation of the payment result notification system)
FIG. 5 is a sequence diagram showing the processing operation of the deposit result notification system according to the present embodiment. The customer accesses the Internet banking server 32 of the financial institution on the destination side (domestic financial institution system 30) from the terminal owned by the customer (the destination side terminal 10) in order to perform overseas remittance. When the customer enters the authentication information and the result of the authentication check is normal, the customer transitions to the overseas remittance dedicated screen. The customer inputs remittance information based on overseas remittance (step S11) and transmits a remittance request to the domestic financial institution system 30 (step S12).

  When the remittance request is received, the remittance server 33 of the domestic financial institution system 30, when performing the payment result notification as a service for a specific customer (premium customer), based on the user ID included in the remittance information, the contractor It is checked whether or not the user is a contractor of this service from a database (not shown) in which information is registered (step S13). Specifically, it is checked whether or not a flag for designating whether or not the remittance for notifying the payment result is set in a predetermined tag of the remittance message. If there is a service contract as a result of the check (step S13 “YES”), the remittance server 33 transmits the remittance information to the account server 35. On the other hand, if there is no service contract as a result of the check (step S13 “NO”), the check result is transmitted to the remittance server 33, and the check result is transmitted from the remittance server 33 to the destination terminal 10. Of course, when the payment result notification is performed for all customers, the check in step S13 is not necessary.

  Next, the account server 35 refers to a database (not shown) in which customer account information is stored, and based on the account information of the customer and the received remittance information, the account balance is insufficient for the remittance amount. A check is made to see if it has been made (step S14). If the check result is NG (step S14 “NG”), the check result is transmitted to the remittance server 33, and the check result is transmitted from the remittance server 33 to the destination terminal 10.

  On the other hand, if the check result is OK (step S14 “OK”), the billing server 35 transmits the check result to the remittance server 33. The remittance message generator 34 generates a remittance message using a standard format (for example, MT 103) based on the remittance information received from the destination terminal 10 (step S15), and stores it in the remittance message DB 100. Note that the remittance server 33 sets the reference number assigned for each remittance request in the tag 20 in the format of the MT 103 in order to associate the payment result notification for each remittance request.

  Next, the remittance server 33 transmits the generated remittance telegram to the AML server 36 and prompts an instruction for AML check. The AML check unit 37 performs an AML check based on the received remittance message (step S16). If the check result is NG (step S16 “NG”), the AML server 36 stores the check result in the check target message DB 200, transmits the check result to the remittance server 33, and checks the remittance server 33 to the destination terminal 10. Send the result. If there is a problem with the check result, the subsequent processing is stopped and the system administrator's judgment is requested.

  On the other hand, if the result of the AML check is OK (step S16 “OK”), the AML server 36 stores the check result in the check target message DB 200 and transmits the check result to the remittance server 33. Then, the remittance server 33 reflects the received check result in the remittance message DB 100, and via the SWIFT connection communication unit 31 to the financial institution (overseas financial institution system 40) of the SWIFT code included in the remittance information via the SWIFT network. Then, a remittance message is transmitted (step S17).

  The remittance server 43 of the overseas financial institution system 40 that has received the remittance message transmits a remittance message decryption instruction to the remittance message decryption unit 44. Then, the remittance message decryption unit 44 decrypts the corresponding remittance message (step S18), and transmits the decrypted remittance message (remittance information) to the AML server 46.

  The AML check unit 47 performs an AML check based on the received remittance information (step S19). Note that the AML check determination process is the same as in step S15.

  If the result of the AML check is OK (step S19 “OK”), the remittance server 43 stores the check result received from the AML server 46 in the remittance message DB 100, and sends the remittance information that is the decrypted remittance message to the accounting server 45. Send. Based on the remittance information, the account server 45 performs a deposit process on the payee account (step S20), and sends a deposit process completion notification to the remittance server 43.

  Next, the remittance server 43 sets the reference number of the original remittance message in the “original transaction number” item of the payment processing completion notification, and transmits the payment processing completion notification to the destination terminal 20 via the Internet 80 (step S21). In addition, a payment processing completion notification is transmitted to the data linkage server 50 via the in-line network 70 (step S22). The customer on the destination side can confirm the payment information or display the payment information through his / her own account or the Internet banking server 42 (step S23), thereby obtaining the receipt confirmation of the overseas remittance.

  On the other hand, upon receipt of the payment processing completion notification from the remittance server 43, the payment result notification unit 51 of the data linkage server 50 saves the payment result data in the payment result information DB 300 (step S24), via the intra-bank network 70 and the like. To the domestic financial institution system 30 (step S25).

  Then, the remittance server 33 of the domestic financial institution system 30 that has received the receipt processing notification extracts the remittance information by referring to the reference number in the receipt processing completion notification, and sends the receipt processing completion notification to the remittance information. The payment result data is stored in the remittance message DB 100 in which the remittance information for each customer is registered, and is reflected in the system (Internet banking server 32) in which the remittance information for each customer is managed (step S26).

  Then, the remittance server 33 transmits a payment process completion notification to the destination terminal 10 via the Internet 80 (step S27). The destination terminal 10 accesses the Internet banking server 32 and determines whether or not the deposit process has been completed for the recipient account of the used overseas remittance from the screen displaying the remittance information including the payment result notification for each overseas remittance. Can be confirmed (step S28). For example, as shown in FIG. 6, a list of overseas remittance information for each customer is displayed as a remittance information display screen, and the received status (Credited) is displayed in the list. With such a screen, it is possible to confirm whether or not the destination customer who made the remittance using the overseas remittance has surely paid the other party.

  As described above, according to the present system, a relay server (data linkage server) serving as a bubbling is provided between the remittance server on the destination side and the remittance server on the destination side (the data linkage server). When the payment process is completed, the payment processing result of the remittance message is received from the destination-side remittance server, and the payment to the payee account based on the remittance request is sent to the destination remittance server. By implementing this mechanism, it is possible to confirm whether or not the destination customer who made the overseas remittance has made a reliable payment to the other party, so that the destination customer receives the funds ( It is possible to know that the money has been securely received by the other party, and to feel secure, so it is possible to construct a convenient overseas remittance system that meets customer requirements.

  As mentioned above, although this invention was demonstrated using embodiment, it cannot be overemphasized that the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiments. Further, it is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

DESCRIPTION OF SYMBOLS 10 Destination side terminal 20 Destination side terminal 30 Domestic financial institution system 31 SWIFT connection communication part 32 Internet banking server 33 Remittance server 34 Remittance message generation part 35 Account server 36 AML server 37 AML check part 38 SWIFT notification server 40 Overseas financial institution System 40 'Non-group financial institution system 41 SWIFT connection communication unit 42 Internet banking server 43 Remittance server 44 Remittance message decryption unit 45 Account server 46 AML server 47 AML check unit 48 SWIFT notification server 50 Data linkage server 51 Deposited result notification unit 60 SWIFT network 70 Internal network 80 Internet 90 Gateway 100 Remittance message database (Remittance message DB)
200 Check target message database (Check target message DB)
300 Deposit Result Information Database (Deposit Result Information DB)

Claims (3)

A destination remittance server connected to the SWIFT network and generating a remittance message based on a remittance request from a destination customer terminal;
A destination-side remittance server connected to the destination-side remittance server and the SWIFT network and depositing a payee account based on the remittance message from the destination-side remittance server;
When the deposit process to the payee account is completed, the remittance server on the destination side and the remittance server on the destination side are connected to the remittance server on the destination side via a network different from the SWIFT network. Data that receives the payment processing result of the remittance message and sends a payment processing completion notification indicating that the payment to the payee account based on the remittance request is completed to the remittance server on the destination side that generated the remittance message With a linkage server,
When the remittance server on the destination side is set to the remittance message when the remittance message is set to indicate whether or not the remittance is to be made, the corresponding remittance server refers to the reference number of the remittance processing completion notice. The remittance information is extracted, the remittance processing completion notification is reflected in the remittance information, the remittance message data is stored in the remittance message DB in which the remittance information for each customer is registered, and the remittance information for each customer is managed. A payment result notification system, wherein the payment result notification is notified to the terminal of the customer on the destination side.   2. The deposit result notification system according to claim 1, wherein the data linkage server is connected as a hub to a destination-side and destination-side remittance server in a plurality of countries or regions. A processing method for notifying a payment result in a payment result notification system comprising a destination-side remittance server, a destination-side remittance server, and a data linkage server,
The destination-side remittance server connected to the SWIFT network generates a remittance message based on a remittance request from a customer destination-side terminal;
The destination-side remittance server connected to the destination-side remittance server and the destination-side remittance server perform a deposit process on a payee account based on the remittance message from the destination-side remittance server;
When the data linkage server completes the deposit process to the payee account, the destination remittance server and the destination remittance server are connected to the SWIFT network via a different network, and the destination Receiving processing result of the remittance message is received from the remittance server on the side, and a remittance processing completion notification indicating that the depositing to the payee account based on the remittance request has been completed is made. Sending to the server;
If the remittance server on the destination side is set to the remittance message to specify whether or not the remittance for notifying the remittance result is made, it is applicable by referring to the reference number of the remittance processing completion notification. The remittance information is extracted, the remittance processing completion notification is reflected in the remittance information, the remittance message data is stored in the remittance message DB in which the remittance information for each customer is registered, and the remittance information for each customer is managed. The steps to be reflected in the system
Notifying the payment result notification to the terminal of the customer on the destination side;
A method for notifying the deposit result, characterized by

Images