Sending realtime payments

Create a saved destination that supports RTP or FedNow, then send USD from an accessible virtual account. If the recipient hasn’t supplied bank details yet, create a queued payment with an informationRequestId instead of a destinationId. Creating a realtime transfer requires a user API key with realtime payment access, used from an allowlisted IP. amount.amount is in minor units, so 1250 USD means USD 12.50.

curl https://api.slash.com/v2/transfers/realtime \
  -X POST \
  -H "X-API-Key: $SLASH_API_KEY" \
  -H "x-legal-entity: $SLASH_LEGAL_ENTITY_ID" \
  -H "X-Idempotency-Key: realtime-invoice-1042" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": { "amount": 1250, "currency": "USD" },
    "fromAccount": "subaccount_operations123",
    "destinationId": "le_contact_destination_bank123",
    "description": "Invoice 1042",
    "realtime": {
      "remittanceInfo": "Invoice 1042"
    }
  }'

The response is a Transfer with type: "realtime". Store its id and retrieve it with GET /v2/transfers/realtime/{transferId}. Cancel with POST /v2/transfers/realtime/{transferId}/cancel while the transfer is still pre-submission. A realtime transfer that isn’t queued, awaiting approval or scheduled is submitted right away, so confirm the destination and amount are correct before initiating a transfer.

Get started

Working with the API

Core objects

Money movement

Cards

Cashback

Bill pay

Invoicing

Accounting

Sending realtime payments