Transfers

The Transfers resource in the Dwolla API enables you to programmatically move funds between accounts. Transfers represent the movement of money from a source (such as a bank or Dwolla balance/wallet) to a destination, and support a variety of use cases—including: pay-ins, pay-outs, facilitating payments between users and enabling transfers between a user’s own accounts (me-to-me). With the Transfers resource, you can initiate, track, and manage payments, handle cancellations, and view detailed transfer statuses and metadata. This resource is central to orchestrating payments, providing transparency and control over the flow of funds in your application.

Transfer Links

Transfer resource

Source and destination types

Source types

Destination types

amount JSON object

Facilitator fee JSON object

The facilitator fee is a feature allowing for a flat rate amount to be removed from a payment as a fee, and sent to the creator of the Dwolla application. The fee does not affect the original payment amount, and exists as a separate Transfer resource with a unique transfer ID. Within a transfer request you can specify an optional fees request parameter, which is an array of fee objects that can represent many unique fee transfers. The fees array is supported on both ACH transfers and Instant Payments transfers.

Facilitator fee example:

"fees": [
  {
    "_links": {
      "charge-to": {
        "href": "https://api-sandbox.dwolla.com/customers/d795f696-2cac-4662-8f16-95f1db9bddd8"
      }
    },
    "amount": {
      "value": "4.00",
      "currency": "USD"
    }
  }
]

clearing JSON object

The clearing object is used in tandem with our expedited transfer feature. This object does not need to be included if not using expedited transfers. Source specifies the clearing time for the source funding source involved in the transfer, and can be used to downgrade the clearing time from the default of Next-day ACH or to upgrade it to Same-day ACH debit. Destination specifies the clearing time for the destination funding source involved in the transfer, and can be used to upgrade the clearing time from the default of Standard ACH to Same-day ACH.

achDetails and addenda object

Note: This feature is only supported for business Customer records.

The addendum record is used to provide additional information to the payment recipient about the payment. This value will be passed in on a transfer request and can be exposed on a Customer’s bank statement. Addenda records provide a unique opportunity to supply your customers with more information about their transactions.

achDetails object

addenda object

achDetails with addenda example:

"achDetails": {
  "source": {
    "addenda": {
      "values": ["ABC123_AddendaValue"]
    }
  },
  "destination": {
    "addenda": {
      "values": ["ZYX987_AddendaValue"]
    }
  }
}

rtpDetails and fedNowDetails objects

When retrieving a transfer from the API, the response will contain either an rtpDetails object or a fedNowDetails object depending on which payment network was used:

• rtpDetails - Included when the transfer was sent via TCH’s RTP Network
• fedNowDetails - Included when the transfer was sent via FRB’s FedNow Service

rtpDetails / fedNowDetails object

destination object

rtpDetails example (RTP Network response):

"rtpDetails": {
  "destination": {
    "remittanceData": "ABC_123 Remittance Data",
    "networkId": "20210617021214273T1BG27487110796028",
    "endToEndReferenceId": "E2E-RTP-20210617-001"
  }
}

fedNowDetails example (FedNow Service response):

"fedNowDetails": {
  "destination": {
    "remittanceData": "ABC_123 Remittance Data",
    "networkId": "20240115123456789FEDNOW123456",
    "endToEndReferenceId": "E2E-FEDNOW-20240115-001"
  }
}

instantDetails object (request only)

The instantDetails object is the recommended way to provide remittance data when initiating an Instant Payment transfer. This object can be used in transfer creation requests regardless of whether the payment ultimately routes via RTP or FedNow.

instantDetails object

destination object

instantDetails example:

"instantDetails": {
  "destination": {
    "remittanceData": "ABC_123 Remittance Data"
  }
}