Wires Workflows

These flowcharts show how wires are created, processed, and returned.

• Outgoing wire
• Outgoing wire return
• Incoming wire
• Incoming wire return

Also see these related guides:

• About Wires — General information about wires
• Creating a Wire Transfer — Instructions for initiating a wire transfer using the Program API.

Outgoing wire

When sending an outgoing wire, the account holder must first create a destination account. Once this account is created, the account holder can reuse it for future wires.

1. The account holder provides destination account information in your interface.
2. You send Create Destination Account to Galileo to create the account.
3. The account holder requests to send funds via wire.
4. You send Create Wire Transaction with the transaction amount and description.
5. Galileo validates the transaction information:
   • If there is an error, the endpoint returns an error message.
   • If the information is valid, Galileo debits the account holder account and sends the BADJ: adj event message with otype: wo.
6. Galileo writes the wire transaction to a batch file.
7. Galileo sends the batch file to a partner bank. These files go out three times per day, currently at 06:00, 10:00, and 13:00, Galileo system time, or according to the schedule set by the partner bank.
8. The partner bank processes the file and sends the wire to Fedwire.
9. Fedwire forwards the transaction to the destination bank.

Outgoing wire return

An outgoing wire can be rejected and returned by Fedwire, the partner bank, or the receiving bank (RDFI). This process may vary depending on the partner bank.

1. Either Fedwire or the receiving bank reject the wire.
2. Fedwire sends the returned wires file to the originating bank (ODFI).
3. The originating bank sends an email notification of the returned wire to you.
4. You send a notification to the account holder that the wire has been returned.
5. You call Create Adjustment to return the funds to the account. Alternatively, you can use the CST to adjust the account.
6. Galileo sends the BADJ: adj event message with otype: WR.

Incoming wire

Galileo supports incoming wires that credit the customer account. Incoming wires arrive periodically at Galileo according to agreements with the partner bank.

1. Fedwire sends the wire to a partner bank.
2. The partner bank sends Galileo the wire transaction.
3. Galileo processes the wire. If the wire transfer does not violate any rules, Galileo credits the customer account with the wire amount.
4. Galileo sends you the BPMT: pmt event message with otype: wi.
5. You notify the account holder that a wire has been received.

Incoming wire return

Galileo might reject an incoming wire for a variety of reasons such as violation of velocity limits, flawed destination-account information, or duplicate transaction.

1. Fedwire sends the wire to a partner bank.
2. The partner bank sends Galileo the wire transaction.
3. Galileo processes the wire. If the wire transfer violates any rules, Galileo rejects the wire and sends you the RTNG: pmt_hub_return event message, provided that the wire can be associated with your program and account. The message contains the return_reason.
4. If the returned wire had the right PRN, you can send a notification to the account holder.
5. Galileo writes the returned wire to a return file and sends it to the partner bank.
6. The bank returns the transaction to Fedwire, which returns it to the originator (ODFI).