> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Queued payments

> Create a payment while the recipient is still supplying payment details.

Queued payments currently support ACH only. Other transfer rails require a
saved `destinationId` when the transfer is created.

Use a queued ACH payment when you know whom to pay but the recipient has not
yet supplied a bank account:

1. Create a Contact with the recipient's email.
2. Create an Information Request asking for a `bank_account` destination.
3. Create the ACH with
   [`POST /v2/transfers/ach`](/api-reference/transfers/ach/create), using
   `informationRequestId` instead of `destinationId`.

`informationRequestId` and `destinationId` are mutually exclusive.

```json theme={null}
{
  "amount": { "amount": 10000, "currency": "USD" },
  "fromAccount": "subaccount_operations123",
  "informationRequestId": "le_c_info_req_vendor123",
  "description": "August vendor payment",
  "ach": { "speed": "standard" }
}
```

The Transfer returns immediately with `status: "pending_destination"` and keeps
the same `transfer_intent_` id throughout the flow. This status does not mean
the payment has settled or that the recipient will complete the request.

Once the recipient supplies a valid destination, Slash attaches it to the
Transfer and continues normal ACH processing. Retrieve the Transfer to observe
the new `destinationId` and status.

Cancel the queued payment with
[`POST /v2/transfers/ach/{transferId}/cancel`](/api-reference/transfers/ach/cancel).
Canceling the Information Request does not cancel a Transfer that already
references it.