Skip to main content
Upcoming ChangeTo support additional Fedwire ISO 20022 mandates, we’re introducing Wires API V2 with structured address requirements and additional wire enhancements.The Fedwire release originally planned for November 2026 has been delayed, and migration to V2 is not required in Q4 2026.The Wires API V2 specification is in preview and can change before sandbox and production release. API release dates will be announced in the Wires API V2 Migration Guide.👉 View V2 Migration Guide
Wire transfers move funds between financial institutions through wire payment networks such as Fedwire. Lead has a direct connection to Fedwire and supports both domestic and international wires through the same API endpoints. Domestic wires sent before Lead’s cutoff generally settle the same business day. International wires may take longer depending on the destination and correspondent banking path. Use wires when you need to send large-dollar, time-sensitive, or international payments. Wires are generally irrevocable once sent. If funds are sent in error, you can request their return, but the receiving financial institution is not obligated to return them. What you can do:
  • Send and receive wires
  • Cancel eligible outgoing wires before they are sent
  • Return incoming wires
  • Send and respond to return requests for posted wires
On this rail:
  • The wire object — all fields and identifiers available on a wire, including agents, identifiers, amounts, and remittance details
  • Wire statuses — how a wire moves through each stage of processing
  • Return requests and Return codes — requesting the return of funds and handling counterparty requests
  • USD international wires — how Lead supports international USD payments
  • Processing windows — cutoff times for sending wires
  • Sandbox — simulating incoming monetary wires, advancing them through the wire lifecycle, and simulating return requests