Overview
Create, list, cancel, or retrieve transfer details.
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
Link | Description |
---|---|
self | URL of the transfer. |
source | GET this link to retrieve the Customer that was the source of the transfer. |
destination | GET this link to retrieve the Customer that was the destination of the transfer. |
source-funding-source | GET this link to retrieve the funding source that was the source of the transfer. |
destination-funding-source | GET this link to retrieve the funding source that was the destination of the transfer. |
cancel | POST to this link to cancel the transfer (A bank transfer is cancellable up until 4pm CT on that same business day if the transfer was initiated prior to 4pm CT. If a transfer was initiated after 4pm CT, it can be cancelled before 4pm CT on the following business day.) |
fees | GET this link to retrieve the facilitator fees associated with the transfer. |
Transfer resource
Parameter | Description |
---|---|
id | Transfer unique identifier. |
status | Either processed , pending , cancelled , or failed . |
amount | An amount JSON object. See below. |
created | ISO-8601 timestamp. |
metadata | A metadata JSON object |
clearing | A clearing JSON object. |
achDetails | An achDetails JSON object. See below. |
rtpDetails | An rtpDetails JSON object. See below. |
correlationId | A string value attached to a transfer resource which can be used for traceability between Dwolla and your application. |
individualAchId | A unique string value matching the value on bank line related to the transfer. Appears when the debit entry clears out of the bank. The individual identifier for that ACH entry. |
processingChannel | A processingChannel JSON object that contains a key-value pair with a string key and string value of destination and real-time-payments . |
Source and destination types
Source types
Source Type | URI | Description |
---|---|---|
Funding source | https://api.dwolla.com/funding-sources/{id} | A bank or balance funding source. |
Destination types
Destination Type | URI | Description |
---|---|---|
Funding source | https://api.dwolla.com/funding-sources/{id} | Destination of an Account or verified Customer’s own bank or balance funding source. OR A Customer’s bank funding source. |
amount JSON object
Parameter | Required | Type | Description |
---|---|---|---|
value | yes | string | Amount of money. If the entered amount has more than two decimal places, Dwolla will automatically round it to the nearest even integer using Banker’s Rounding. Maximum limit: Default transaction limits based on Customer type or custom transaction limits as defined in the services agreement with Dwolla. Minimum limit: $0.01. |
currency | yes | string | Possible values: USD |
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.
Facilitator Fee Overview
For more information on collecting fees on payments, reference the facilitator fee resource article.
Parameter | Description |
---|---|
_links | Contains a charge-to JSON object with a link to the associated source or destination Customer resource. |
amount | Amount of fee to charge. An amount JSON object. See above |
Facilitator fee example:
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.
The clearing request parameter is a premium feature available for Dwolla customers in the Scale pricing tier. Enabling Next-day ACH and Same-day ACH requires additional Dwolla approvals before getting started. Please contact sales or your account manager for more information on enabling this feature.
Parameter | Required | Type | Description |
---|---|---|---|
source | no | string | Represents a clearing object for debits into the Dwolla network. Possible values: standard , next-available standard - Used to downgrade the clearing time of debits from the default of Next-day ACH (if enabled) to Standard ACH. next-available - Used to upgrade the clearing time of debits to Same-day ACH. |
destination | no | string | Represents a clearing object for credits out of the Dwolla network to a bank funding source. Possible values: next-available next-available - Used to upgrade the clearing time of credits to Same-day ACH. |
Clearing examples:
Standard debit and Same-day credit (when Next-day is enabled)
Next-day debit and Same-day credit (when Next-day is enabled)
Same-day debit and Same-day credit
Same-day debit and Standard credit
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. Allowing businesses to include additional details about the transaction—such as invoice numbers—provides their end users with more information about the transaction in the comfort of their own banking application.
achDetails object
Parameter | Required | Type | Description |
---|---|---|---|
source | no | object | Represents information that is sent to a source/originating bank account along with a transfer. Include information within this JSON object for customizing details on ACH debit transfers. Can include an addenda JSON object. |
destination | no | object | Represents information that is sent to a destination/receiving bank account along with a transfer. Include information within this JSON object for customizing details on ACH credit transfers. Can include an addenda JSON object. |
addenda object
Parameter | Required | Type | Description |
---|---|---|---|
addenda | no | object | An addenda object contains a values key where its value is an array containing a single string addenda value. Addenda record information is used for the purpose of transmitting transfer-related information from a business. Addenda value must be less than or equal to 80 characters and can include spaces. Acceptable characters are: a-Z, 0-9, and special characters - _ . ~ ! * ' ( ) ; : @ & = + $ , / ? % # [ ] . Transfers must be sent to/from a business entity’s bank to guarantee addenda delivery. |
achDetails with addenda example:
rtpDetails object
Note: This is available as part of RTP®, a premium feature available for Dwolla customers. Enabling RTP® does require additional Dwolla approvals before getting started. Please contact Sales or your account manager for more information on enabling this account feature.
The rtpDetails
object is used to provide additional information to the payment recipient about their RTP® credit transfer. This value will be passed in on an RTP® credit transfer request to the recipient’s bank account.
Refer to our Real-time Payments developer concept article to learn more about initiating an RTP® credit transfer.
rtpDetails object
Parameter | Required | Type | Description |
---|---|---|---|
destination | no | object | Represents information that is sent to a destination/receiving bank account along with an RTP® credit transfer. Include information within this JSON object for customizing details on RTP® credit transfers. Contains a key-value pair for remittanceData . |
destination object
Parameter | Required | Type | Description |
---|---|---|---|
remittanceData | no | string | Contains a string value. Used for the purpose of transmitting RTP® transfer-related information to the recipient’s bank account. RTP® remittance data value must be less than or equal to 140 characters and can include spaces. |