JP2021077417A - Remittance support system, remittance support method, and remittance support program - Google Patents

Abstract

To provide a remittance support system, a remittance support method, and a remittance support program for supporting remittances from overseas.SOLUTION: A management server 20 is configured to receive, from a user terminal 15, payment data including a transit identifier, an account identifier of a payee account, and information on an amount of payment, identify a customer identifier associated with the transit identifier included in the payment data using a transit information storage unit 22, set the customer identifier in the transit information storage unit 22 as a payer name based on a purpose of remittance corresponding to the payment data to a bank host system 30 that has received payment data including the transit identifier from an overseas financial institution system 10, and instruct to transfer money from a source account corresponding to the transit identifier to the payee account included in the payment data.SELECTED DRAWING: Figure 1

Description

The present invention relates to a remittance support system, a remittance support method, and a remittance support program for supporting remittance from overseas.

When receiving a payment instruction to a domestic customer from an overseas bank by remittance message, the remittance amount is deducted from the correspondent account of the remittance bank and deposited in the customer account. For such remittances, the remittance message created using the format standardized by the International Standardization Organization is used as the International Interbank Communication System (SWIFT®: The Society for Worldwide Interbank Financial Tele-communication). Receive via (see, for example, Patent Document 1). In this technology, when the remittance server on the destination side receives the information necessary for overseas remittance from the customer, it generates a remittance message based on the necessary items. Then, based on the generated remittance message, it is transmitted to the remittance server on the recipient side via the SWIFT network. The remittance server on the recipient side decodes the received remittance message and executes the payment process to the customer account on the recipient side of the remittance destination based on the remittance information included in the remittance message. When the deposit processing is completed, the recipient's remittance server processes the deposit to the data linkage server, which serves as the hub for data linkage between the systems of the financial institution's bases in each country and region, via an in-bank network separate from the SWIFT network. Send a completion notification. In response to this, the data linkage server sends the received payment processing completion notification to the remittance server on the destination side via the above-mentioned in-bank network.

Japanese Unexamined Patent Publication No. 2016-12265

In the case of a company that has an account at a domestic financial institution, it is possible to make an account transfer to a domestic recipient from this account. On the other hand, when a foreign company that does not have a domestic account pays to a domestic recipient, it is necessary to use foreign exchange remittance. In this case, the burden of foreign exchange remittance is large.

The remittance support system that solves the above problems includes a passage information storage unit that stores a passage identifier and a customer identifier in association with each other, a bank host system that communicates with an overseas financial institution system, and a control unit that is connected to a user terminal. Then, the control unit receives the deposit data including the passage identifier from the overseas financial institution system, and is associated with the passage identifier included in the payment data from the user terminal using the passage information storage unit. Based on the purpose of remittance corresponding to the payment data in the passage information storage unit, the customer identifier is specified and the payment data including the passage identifier is received from the overseas financial institution system to the bank host system. From the remittance source account corresponding to the passage identifier, the customer identifier is set as the payer name, and a transfer instruction is given to the payee account included in the payment data.

According to the present invention, it is possible to support efficient and accurate remittance from a foreigner who does not have an account at a domestic financial institution to a domestic resident.

The system schematic diagram of this embodiment. Explanatory drawing of hardware configuration example. It is explanatory drawing of the data used in this embodiment, (a) is a passage information storage unit, (b) is a payment information storage unit, and (c) is an explanatory diagram of a deposit information storage unit. The explanatory view of the processing procedure of this embodiment. The explanatory view of the processing procedure of this embodiment.

Hereinafter, an embodiment in which the remittance support system, the remittance support method, and the remittance support program are embodied will be described with reference to FIGS. 1 to 5. In this embodiment, it is assumed that a remittance request is received from an overseas financial institution and a service of depositing money into an account held by a domestic recipient is provided.

As shown in FIG. 1, in the remittance support method of the present embodiment, an overseas financial institution system 10, a user terminal 15, a management server 20, and a bank host system 30 that are interconnected via a network are used.

(Hardware configuration example)
FIG. 2 is a hardware configuration example of the information processing device H10 that functions as an overseas financial institution system 10, a user terminal 15, a management server 20, a bank host system 30, and the like.

The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage unit H14, and a processor H15. Note that this hardware configuration is an example, and other hardware may be included.

The communication device H11 is an interface that establishes a communication path with another device and executes data transmission / reception, such as a network interface card or a wireless interface.

The input device H12 is a device that receives input from a user or the like, and is, for example, a mouse, a keyboard, or the like. The display device H13 is a display, a touch panel, or the like that displays various information.

The storage unit H14 is a storage device (for example, a passage information storage unit 22 described later) that stores data and various programs for executing various functions of the overseas financial institution system 10, the user terminal 15, the management server 20, and the bank host system 30. , Payment information storage unit 23, account information storage unit 32, deposit information storage unit 33). An example of the storage unit H14 is a ROM, a RAM, a hard disk, or the like.

The processor H15 uses programs and data stored in the storage unit H14 to control each process (for example, a process in the control unit 21 described later) in the information processing device H10 that functions as a management server 20, a bank host system 30, and the like. To do. Examples of the processor H15 include a CPU, an MPU, and the like. The processor H15 expands a program stored in a ROM or the like into a RAM and executes various processes corresponding to various processes. For example, when the application programs of the overseas financial institution system 10, the user terminal 15, the management server 20, and the bank host system 30 are started, the processor H15 operates a process for executing each process described later.

The processor H15 is not limited to the one that performs software processing for all the processing executed by itself. For example, the processor H15 may include a dedicated hardware circuit (for example, an integrated circuit for a specific application: ASIC) that performs hardware processing for at least a part of the processing executed by the processor H15. That is, the processor H15 is (1) one or more processors that operate according to a computer program (software), (2) one or more dedicated hardware circuits that execute at least a part of various processes, or ( 3) It can be configured as a circuitry including a combination thereof. The processor includes a CPU and a memory such as a RAM and a ROM, and the memory stores a program code or an instruction configured to cause the CPU to execute a process. Memory or computer-readable media includes any available medium accessible by a general purpose or dedicated computer.

(Functions of each information processing device)
The overseas financial institution system 10 shown in FIG. 1 is a computer system owned by an overseas financial institution for remittance. The overseas financial institution system 10 is connected to the bank host system 30 via the SWIFT network.

The user terminal 15 is a computer terminal owned by a customer who makes a remittance request. The user terminal 15 is connected to the management server 20 via a network such as the Internet.

The management server 20 is a computer system that supports a remittance service from an overseas remittance sender to a domestic remittance recipient. The management server 20 includes a control unit 21, a passage information storage unit 22, and a payment information storage unit 23.

The control unit 21 functions as the payment management unit 211 and the refund management unit 212 by executing the remittance support program.
The payment management unit 211 receives payment data from the user terminal 15 via the Internet and executes a process of making a transfer.
The refund management unit 212 executes a process of managing refunds to the overseas financial institution system 10.

As shown in FIG. 3A, the passage information storage unit 22 records a passage management record 220 for managing an account that associates deposit data with payment data. This transit management record 220 is recorded when a transit account is set. The passage management record 220 records information regarding the passage identifier, customer name, remittance purpose, and refund conditions.

In the passage identifier data area, data regarding identifiers (bank identifier, head office / branch identifier, deposit type identifier, account number) for identifying an account for temporarily storing funds remitted from overseas payers is recorded. .. In the present embodiment, a savings account in the name of the bank is used as the passing account.

In the customer name data area, data regarding a name (customer identifier) for identifying an overseas customer who uses this passing account is recorded.
In the remittance purpose data area, data regarding the purpose of remittance using this transit account is recorded. For this remittance purpose, the remittance purpose that needs to be managed in the remittance from "overseas" is recorded.

The refund conditions data area records data regarding the conditions for refunding to this payer. Refund terms include elements for determining whether or not a refund is required. As this element, for example, the number of non-transferable cases, the non-transferable amount, the timing of refund, the calculation method of the refund amount, and the like can be used.

As shown in FIG. 3B, the payment information storage unit 23 records a payment management record 230 relating to payment data received from the user terminal 15 via the Internet. The payment management record 230 is recorded when payment data is received. The payment management record 230 records data on the transit identifier, the payee account, the payment amount, the contact information, and the remittance result.

In the transit identifier data area, data regarding identifiers for comprehensively identifying remittances from overseas payers is recorded. In this embodiment, the account identifier of the passing account is used.
In the beneficiary account data area, data regarding an identifier (bank identifier, head office identifier, deposit type identifier, account number) for identifying the recipient's account is recorded.

In the payment amount data area, data regarding the amount to be deposited in the payee account is recorded.
In the contact data area, data regarding the contact (address) of the payer's user terminal 15 is recorded.

A flag is recorded in the remittance result data area to identify the remittance result for this payment. When the remittance is completed, the completion date is recorded, and when the remittance cannot be made due to insufficient balance of the passing account, the insufficient balance flag is recorded. If the payee account cannot be identified, the non-transferable flag is recorded.

The bank host system 30 is a computer system of a domestic financial institution that manages the accounts of customers (payers and payees) of the financial institution. This financial institution includes not only its own bank but also other banks. The bank host system 30 includes a control unit 31, an account information storage unit 32, and a deposit information storage unit 33.

The control unit 31 functions as an account management unit 311 and a deposit management unit 312 by executing the account processing program.
The account management unit 311 executes a process of managing an account opened in a bank.
The deposit management unit 312 executes a process of transmitting and receiving deposit data and the like from the overseas financial institution system 10 via the SWIFT network.

The account information storage unit 32 records account management information for managing an account opened in a financial institution. In this account management information, an account identifier, an account holder, a balance, and a deposit / withdrawal history are recorded.

In the account identifier data area, data related to an identifier (bank identifier, head office / branch identifier, deposit type identifier, account number) for identifying an account opened in a financial institution is recorded. In the present embodiment, the passing account is also included in the account opened in the financial institution.
In the account holder data area, data regarding an identifier for identifying the holder (payer or payee) of this account is recorded. In this embodiment, the transit account is in the name of the bank.
Data regarding the balance of this account is recorded in the balance data area.
In the deposit / withdrawal history data area, history information of deposits to / from this account and withdrawals from this account is recorded.

As shown in FIG. 3C, the deposit information storage unit 33 records the deposit management record 330 relating to the deposit data received from the overseas financial institution system 10 via the SWIFT network. The deposit management record 330 is recorded when the deposit data is received. Data regarding the remittance source account, the remittance destination account, the remittance amount, and the remittance purpose are recorded in the remittance management record 330.

In the remittance source account data area, data relating to an identifier for identifying the remittance source account from the overseas financial institution system 10 is recorded.
In the remittance destination account data area, data regarding an identifier for identifying a remittance destination account from the overseas financial institution system 10 is recorded.
In the remittance amount data area, data regarding the amount of money remitted from an overseas payer is recorded.
Data regarding the purpose of this remittance is recorded in the remittance purpose data area.

(Payment management process)
Next, the payment management process will be described with reference to FIG. When using a transit account, the bank host system 30 opens a transit account in the name of the bank according to the payer and the purpose of remittance. Then, the management server 20 generates a passage management record 220 that records the passage identifier, the customer name, the purpose of remittance, and the refund condition, and records it in the passage information storage unit 22.

First, the control unit 31 of the bank host system 30 executes the payment processing of the transfer payment (step S1-1). Specifically, the deposit management unit 312 of the control unit 31 receives the deposit data via the SWIFT network. This deposit data includes data on the remittance source account, remittance destination account, remittance amount, and remittance purpose according to the SWIFT format. The deposit data may not include the purpose of remittance. Then, the deposit management unit 312 generates a deposit management record 330 in which the information included in the deposit data is recorded, and records the information in the deposit information storage unit 33. Next, the account management unit 311 performs a process for depositing the remittance amount to the remittance destination account. When using this service, the money will be credited to the transit account as the remittance destination account.

Further, the control unit 21 of the management server 20 executes a payment data reception process according to the purpose of remittance (step S1-2). Specifically, the payment management unit 211 of the control unit 21 receives payment data via the Internet. This payment data includes data on transit identifiers, payee accounts, and payment amounts. In the case of a plurality of payments (for example, thousands) in which a plurality of recipients exist, the payment amount is set for each recipient account. Then, the payment management unit 211 generates a payment management record 230 that records the information included in the payment data, and records it in the payment information storage unit 23. At this stage, the remittance result data area of the payment management record 230 is left blank.

Next, the control unit 21 of the management server 20 repeats the following processing for each payment.
Here, the control unit 21 of the management server 20 executes the process of specifying the passing account (step S1-3). Specifically, the payment management unit 211 of the control unit 21 identifies the passing account by using the passing identifier included in the payment management record 230.

Next, the control unit 21 of the management server 20 executes the balance check process of the passing account (step S1-4). Specifically, the payment management unit 211 of the control unit 21 acquires the balance of the specified passing account from the bank host system 30.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not the balance is sufficient (step S1-5). Specifically, the payment management unit 211 of the control unit 21 compares the balance of the passing account with the payment amount included in the payment management record 230. Then, when the balance is equal to or more than the payment amount, it is determined that the balance is sufficient.

When it is determined that the balance is sufficient (when "YES" in step S1-5), the control unit 21 of the management server 20 executes the transfer message creation process (step S1-6). Specifically, the payment management unit 211 of the control unit 21 acquires the customer name recorded in the passage management record 220 of the passage identifier from the passage information storage unit 22. Then, the payment management unit 211 generates a transfer message for domestic remittance. In this transfer message, the account identifier of the passing account is set in the destination account column, the customer name is set in the transferee column, the payee account identifier is set in the destination account column, and the payment amount is set in the transfer amount column. Then, the payment management unit 211 transmits the created transfer message to the bank host system 30. As a result, the bank host system 30 executes the remittance process.

Next, the control unit 21 of the management server 20 executes the transfer result recording process (step S1-7). Specifically, the payment management unit 211 of the control unit 21 acquires the transfer result from the bank host system 30. The transfer result includes information for identifying the completion or non-transferability of the transfer to the payee's account. When the transfer result includes the transfer completion information, the payment management unit 211 records the completion date in the remittance result data area of the payment management record 230. On the other hand, when the non-transferable information is included, the payment management unit 211 records the non-transferable flag in the remittance result data area of the payment management record 230.

On the other hand, when it is determined that the balance is not sufficient because the balance is less than the remittance amount (when "NO" in step S1-5), the control unit 21 of the management server 20 executes error processing (step S1-8). ). Specifically, the payment management unit 211 of the control unit 21 records the balance shortage flag in the remittance result data area of the payment management record 230.
The control unit 21 of the management server 20 repeats the above processing for each payment.

Next, the control unit 21 of the management server 20 executes a reply process of the transfer result data (step S1-9). Specifically, the payment management unit 211 of the control unit 21 acquires the remittance result of the payment management record 230 in which the passage identifier is recorded from the payment information storage unit 23. Then, the payment management unit 211 generates the transfer result data in which the remittance result is recorded in association with the payee account identifier. If the payment data includes a plurality of payments to a plurality of recipients, the transfer result data is collectively generated. Then, the payment management unit 211 identifies the address of the payer's user terminal 15 and transmits the transfer result data. The reply of the transfer result data is not limited to the case of sending to the payer's address. For example, the transfer result data may be uploaded to a specific server so that it can be downloaded after the recipient authentication process.

(Refund management process)
Next, the refund management process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes the payment status specifying process (step S2-1). Specifically, the refund management unit 212 of the control unit 21 searches the payment information storage unit 23 for the payment management record 230 for which payment has not been made. Here, the payment information storage unit 23 identifies the payment management record 230 in which the non-transferable flag is recorded.

Next, the control unit 21 of the management server 20 executes the refund necessity determination process (step S2-2). Specifically, the refund management unit 212 of the control unit 21 acquires the refund condition from the passage information storage unit 22. Then, the refund management unit 212 identifies an element for determining the refund condition and acquires status information related to this element. When the number of non-transferable cases is set as an element, the number of records of the payment management record 230 in which the non-payable flag is recorded is calculated. When the non-transferable amount is set as an element, the total amount of the payment amount of the payment management record 230 in which the non-payable flag is recorded is calculated. If the refund period is set as an element, compare it with the current date.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not a refund is required (step S2-3). Specifically, the refund management unit 212 of the control unit 21 determines that a refund is necessary when the status information satisfies the refund conditions.

When it is determined that refund is necessary (when "YES" in step S2-3), the control unit 21 of the management server 20 executes refund processing of the balance that cannot be transferred (step S2-4). Specifically, the refund management unit 212 of the control unit 21 calculates the refund amount according to the refund conditions, and sends a remittance instruction regarding the balance of the passing account to the bank host system 30. In this case, the payment management unit 312 of the control unit 31 remits money to the payer's account.

On the other hand, when the status information does not satisfy the refund conditions and it is determined that refund is unnecessary (when "NO" in step S2-3), the control unit 21 of the management server 20 refunds the balance that cannot be transferred (step). Skip S2-4) and end the refund management process.

According to this embodiment, the following effects can be obtained.
(1) In the present embodiment, the passage information storage unit 22 records a passage management record 220 for managing an account that associates deposit data and payment data. This transit management record records information about the transit identifier, customer name, remittance purpose, and refund conditions. An overseas payer can use this transit identifier to make a payment to a domestic payee. Therefore, the payer can save the trouble of holding an account at a domestic financial institution. Further, since the transit account is set for each payer and remittance purpose, different payers and remittance purposes can be distinguished and managed accurately.

(2) In the present embodiment, the control unit 21 of the management server 20 executes the process of specifying the passing account (step S1-3). The control unit 21 of the management server 20 executes a determination process as to whether or not the balance is sufficient (step S1-5). When it is determined that the balance is sufficient (when "YES" in step S1-5), the control unit 21 of the management server 20 executes the transfer message creation process (step S1-6). As a result, the funds received by one deposit data can be remitted to a plurality of recipients by using the payment data.

(3) In the present embodiment, the payment management unit 211 generates a transfer message for domestic remittance. In this transfer message, the account identifier of the passing account is set in the destination account column, the customer name is set in the transferee column, the payee account identifier is set in the destination account column, and the payment amount is set in the transfer amount column. As a result, it is possible to make a transfer with an overseas customer name while using a passing account.

(4) In the present embodiment, the control unit 21 of the management server 20 executes the return processing of the transfer result data (step S1-9). As a result, the payer can grasp the payment status.

(5) In the present embodiment, the control unit 21 of the management server 20 executes the refund necessity determination process (step S2-2). As a result, the payer can be refunded according to the refund conditions. For example, if a large amount of account balance is maintained for payment, refunds can be made depending on the situation. In addition, even if the transfer cannot be made due to an inadequate payee account, the payer can be efficiently refunded depending on the situation.

This embodiment can be modified and implemented as follows. The present embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
-In the above embodiment, an identifier for identifying an account for temporarily storing funds remitted from an overseas payer is used as a passing identifier. The transit identifier is not limited to the account identifier of the transit account. For example, the remittance source account may be specified by using an identifier that can specify each deposit for each purpose of remittance.

-In the above embodiment, a savings account in the name of the bank is used as the transit account, but the holder and the type of deposit are not limited to this.
-In the above embodiment, when it is determined that the transfer is not possible (when "YES" in step S2-1), the control unit 21 of the management server 20 executes the refund necessity determination process (step S2-2). Refund methods are not limited to this. For example, the payer may be asked whether or not a refund is required each time a transfer is not possible.

-In the above embodiment, the passage management record 220 of the passage information storage unit 22 records information regarding the passage identifier, the customer name, the purpose of remittance, and the refund conditions. The information recorded in the passage information storage unit 22 is not limited to these. For example, the purpose of remittance and refund conditions may not be recorded in the passing information storage unit 22. In this case, the control unit 21 of the management server 20 deposits money in the passing account without being limited to the purpose of remittance. Then, the control unit 21 of the management server 20 acquires the remittance purpose from the recipient and performs the remittance according to the remittance purpose. Also, regarding the refund conditions, refunds may be made when requested by the remittance sender.
Further, as a refund condition, the account balance of the passing account may be used. For example, if the balance of the passing account is equal to or more than the standard amount and is maintained for a predetermined period, the refund may be made. In addition, the unpaid payment management record 230 in which the remittance result data area is blank or the balance shortage flag is recorded is specified, and the difference between the total amount of unpaid payments and the account balance is equal to or greater than the standard amount as a refund condition. You may.

-In the above embodiment, the control unit 21 of the management server 20 executes a balance check process of the passing account (step S1-4) and a determination process of determining whether the balance is sufficient (step S1-5). Then, when it is determined that the balance is sufficient (when "YES" in step S1-5), the control unit 21 of the management server 20 executes the transfer message creation process (step S1-6). Instead of this, the control unit 21 of the management server 20 may execute the transfer message creation process (step S1-6) without performing the balance check process of the passing account. Then, when the balance of the passing account is insufficient, the transfer impossible information due to the insufficient balance is acquired from the bank host system 30.

10 ... Overseas financial institution system, 15 ... User terminal, 20 ... Management server, 21 ... Control unit, 211 ... Overseas remittance department, 212 ... Payment management department, 22 ... Passing information storage unit, 23 ... Payment information storage unit, 30 ... Bank host system, 31 ... control unit, 311 ... account management unit, 312 ... deposit management unit, 32 ... account information storage unit, 33 ... deposit information storage unit.

Claims (6)

A transit identifier consisting of the account identifier of the remittance source account, which is a deposit account in the name of a financial institution, a transit information storage unit stored in association with a customer identifier, and
A remittance support system equipped with a bank host system that communicates with an overseas financial institution system and a control unit connected to the payer's user terminal.
The control unit
From the user terminal, payment data including the passage identifier of the deposit account for temporarily storing the funds remitted from the payer, the account identifiers of a plurality of payee accounts, and the information on the payment amount is received.
The pass information storage unit is used to identify the customer identifier associated with the pass identifier included in the payment data.
Based on the remittance purpose corresponding to the deposit data to the bank host system that received the deposit data including the passage identifier from the overseas financial institution system, the passage from the remittance source account corresponding to the passage identifier. A remittance support system characterized in that a plurality of transfer messages in which the customer identifier of the information storage unit is set as a payer name are generated, and a transfer instruction is given to each payee account included in the payment data. The control unit
Comparing the balance of the remittance source account with the payment amount included in the payment data,
The remittance support system according to claim 1, wherein when the balance is insufficient with respect to the payment amount, the user terminal of the customer associated with the passage identifier is contacted. In the passage information storage unit, refund conditions are recorded in association with the passage identifier, and the refund conditions are recorded.
The remittance support system according to claim 1 or 2, wherein the control unit executes refund processing based on the refund conditions according to the processing result of transfer processing according to the payment data. The refund terms include information about the balance of the remittance source account.
The remittance support system according to claim 3, wherein the control unit identifies the balance of the remittance source account and executes a refund process according to the balance. A transit identifier consisting of the account identifier of the remittance source account, which is a deposit account in the name of a financial institution, a transit information storage unit stored in association with a customer identifier, and
This is a method of supporting remittance using a bank host system that communicates with an overseas financial institution system and a remittance support system that has a control unit connected to the payer's user terminal.
The control unit
From the user terminal, payment data including the passage identifier of the deposit account for temporarily storing the funds remitted from the payer, the account identifiers of a plurality of payee accounts, and the information on the payment amount is received.
The pass information storage unit is used to identify the customer identifier associated with the pass identifier included in the payment data.
Based on the remittance purpose corresponding to the deposit data to the bank host system that received the deposit data including the passage identifier from the overseas financial institution system, the passage from the remittance source account corresponding to the passage identifier. A remittance support method characterized in that a plurality of transfer telegrams in which the customer identifier of the information storage unit is set as a payer name are generated, and a transfer instruction is given to each payee account included in the payment data. A transit identifier consisting of the account identifier of the remittance source account, which is a deposit account in the name of a financial institution, a transit information storage unit stored in association with a customer identifier, and
A program that supports remittance using a bank host system that communicates with an overseas financial institution system and a remittance support system that has a control unit connected to the payer's user terminal.
The control unit
From the user terminal, payment data including the passage identifier of the deposit account for temporarily storing the funds remitted from the payer, the account identifiers of a plurality of payee accounts, and the information on the payment amount is received.
The pass information storage unit is used to identify the customer identifier associated with the pass identifier included in the payment data.
Based on the remittance purpose corresponding to the deposit data to the bank host system that received the deposit data including the passage identifier from the overseas financial institution system, the passage from the remittance source account corresponding to the passage identifier. A remittance support program characterized by generating a plurality of transfer messages in which the customer identifier of the information storage unit is set as a payer name and functioning as a means for instructing a transfer to each payee account included in the payment data.

Images