Skip to main content
A wire passes through two stages. Before submission it waits for anything that has to happen first: approval, a scheduled time, or the recipient’s bank details. Submission and settlement then covers the wire from the moment it is queued for bank submission until it reaches a final status.

Before submission

Approval, scheduling, and queuing each add a status before submission, always in this order. A wire skips any that don’t apply:
  • pending_approval while a required approver has not acted
  • scheduled while waiting for the scheduled time. Wires created through the API are never scheduled; this status appears for wires scheduled in the dashboard.
  • pending then pending_destination for a queued payment: pending while Slash places a hold on the source account, then pending_destination once the funds are held and until the recipient answers the information request and claims the payment
A queued payment is pending twice. First, Slash is placing a hold on the source account and nothing has been sent to the bank. After the recipient claims the payment, it is pending again, now queued for bank submission. If the hold can’t be placed, the wire becomes failed.
Wire transfer before submissionWire transfer before submission

Combinations

Each row is one combination and the statuses a wire passes through before it is queued for bank submission.

Submission and settlement

This chart picks up where the one above ends: at pending, queued for bank submission. A wire can pause in in_review. It then becomes:
  • settled after successful completion
  • failed if it does not complete
  • canceled if it is canceled before submission (see Canceling)
  • returned if the beneficiary bank later sends the funds back
Wire transfer submission and settlementWire transfer submission and settlement

Canceling

Cancel with POST /v2/transfers/wire/{transferId}/cancel while the wire is still pre-submission, including destination, approval, review, and scheduling holds. Once the wire has been sent to the bank, cancellation returns 409. Cancellation is idempotent after it succeeds. A rejected approval also ends the wire as canceled, and Slash can cancel a wire before submission.

Tracking status

Network identifiers appear as they become available: wire.imad and wire.omad. Poll GET /v2/transfers/wire/{transferId} or use the webhook’s entityId to retrieve a Transaction, then follow its transferId.