Keep up to date on new product features and enhancements, API docs, tools changes, and development updates.
instant
or real-time-payments
as the processingChannel.destination
value. Dwolla intelligently selects between RTP and FedNow based on availability and configuration.instantDetails
as the preferred method for passing remittance data, while maintaining backward compatibility with rtpDetails
.rtpDetails
(for RTP transfers) or fedNowDetails
(for FedNow transfers) with identical structure including networkId
, endToEndReferenceId
, and remittanceData
.customer_funding_source_rtp_enabled
/customer_funding_source_rtp_disabled
) now cover both RTP and FedNow eligibility changes._embedded.errors
array of the Retrieve a Customer response for Business Verified Customers. These directives provide actionable guidance and relevant links to help resolve verification issues. See the new Understanding Verification Directives section in the Business Verified Customer guide.customer_verification_pending_review
customer_address_verification_failed
customer_verified
, customer_verification_document_needed
, customer_reverification_needed
and customer_suspended
)/sandbox-simulations
endpoint. See the Sandbox testing guide for details on how to test these scenarios and webhook events.externalProviderSessionToken
to the response to accommodate Plaid-specific information, such as Plaid link token.plaid
JSON object containing a Plaid publicToken
.customer_exchange_reauth_required
, an exchange related event specific to Plaid. This webhook will be triggered when a user’s bank connection has been interrupted or is requiring re-authentication in order to ensure continued access to the user’s financial data.ValidationError
with an Invalid
code and message of The provided redirect URL must exactly match one of the configured URLs for the account
.retry-with-full-ssn
link to the Customer resource. This link appears whenever retry information is required for the Controller in order to verify the business verified Customer.dwolla.js
library, which supported adding an unverified bank funding source. Check out the official announcement./customers/{id}/iav-token
and /customers/{id}/funding-sources-token
.correlationId
attribute to the webhook payload for transfer related webhooks if a value was specified on transfer creation.ForeignPassportNotAllowed
, for when a foreign passport is uploaded for Personal Verified Customers. Foreign passports are still accepted when uploaded for Business Controllers or Beneficial Owners.ScanIdUnrecognized
, for both business and personal customers.documentVerificationStatus
field to the document resource. This field indicates the status of the document after it has been reviewed by Dwolla. Possible values include pending
, accepted
and rejected
.upload-dba-document
link to the Customer resource. This link appears whenever a DBA (Doing Business As) document is required from the Customer to verify their business._embedded
object to the Customer resource which contains a list of errors related to getting the Customer verified. The _embedded
object appears whenever the Customer is in retry
or document
.Add a Debit Card
form in dwolla-cards.js
. This enables the form to display helpful error messages to the user whenever they enter invalid data.BusinessDocNotSupported
, BusinessNameMismatch
, BusinessTypeMismatch
.ScanFailedOther
and ScanNameMismatch
to provide more details about the failure reason.document
status for Business Verified Customers in Sandbox. Check out our Testing in the Sandbox guide to learn more.verified
status to become unverified
..pdf
. A validation error will be returned with a code
of "Invalid"
and a message
of "Invalid file type"
.document
status. If a request to upload a duplicate document is sent, it will fail with a validation error response that includes a link to the existing uploaded document for the Customer.clearing
JSON object when creating a mass payment.clearing
object allows for the clearing time of individual mass payment items to be upgraded or downgraded from the default ACH processing time.allFailureReasons
to the Document resource, which helps with further identifying the reason for the rejection of an identity verification document uploaded for a Verified Customer.total
attribute to the Balance object in the API.Labels
resource to the API.traceId
to the achDetails
object within the Transfer resource, which helps with further identifying a transfer to/from a user’s bank account.
Jump to our API Docs.https://www.dwolla.com/oauth/v2/token
and specified the application/x-www-form-urlencoded
Content-Type
header, passing their client credentials (App Key and App Secret) through the body of the HTTP message sent to Dwolla.https://api.dwolla.com/token
.tif
file upload.funding_source_negative
and customer_funding_source_negative
EmptyResponse
instead of object
in DwollaClient interface.UnsupportedBank
).customer_balance_inquiry_completed
event. Upon checking a Customer’s bank balance, Dwolla will immediately return an HTTP 202 with response body that includes a status of processing. This event will be triggered when the bank balance check has completed processing. To read more on how to trigger this event, check out our forum post.customer_bank_transfer_creation_failed
event. This event will be triggered when an attempt to initiate a transfer to a verified Customer’s bank was made, but failed. Transfers initiated to a verified Customer’s bank must pass through the verified Customer’s balance before being sent to a receiving bank. Dwolla will fail to create a transaction intended for a verified Customer’s bank if the funds available in the balance are less than the transfer amount. To read more on how to trigger this event, check out our forum post.backButton
and subscriber
options for IAV within dwolla.js. Note: Dwolla.js is a premium feature only available for Dwolla API customers.https://sandbox-uat.dwolla.com/
clearing
request parameter when initiating a transfer. Clearing is a JSON object that supports specifying same-day and standard ACH clearing per API request. Note: The clearing request parameter is a premium feature available for Dwolla API customers.scope
attribute from the application access token response.phone
request parameter from required to optional when creating a Customer.bankName
attribute to the funding source object that is returned when retrieving a funding source of type bank.profileId
request parameter from the Off-Site Gateway in API v1.Idempotency-Key
header on requests to API v2.DELETE
to a POST
with the need to supply {"removed": true}
in the body of the request.removed
attribute is added to the funding source object.removed
querystring request parameter is supplied when listing an Account or Customer’s funding sources. By default, all funding sources are returned from the listing unless the removed
request parameter is set to false
.description
field in API v2 error responses. Replacing description with the message
field which is a duplication of description.X-Request-Signature
header from webhook requests. Replacing with a X-Request-Signature-SHA-256
header which is a SHA-256 HMAC hash of the request body with the key being your webhook secret.POST /business-classifications
POST /business-classifications/{id}
POST /customers/{id}/funding-sources-token
GET /transfers/{id}failure
POST /customers/{id}/iav-token
dwolla.js
to the CDN. https://cdn.dwolla.com/1/dwolla.js
message
field in error response. Errors now include a profile
link in the Content-Type
header. Error responses with the top-level error code ValidationError
will return an _embedded
object containing a list of errors.redirect_uri
must match the OAuth Redirect URL field set in Dwolla application’s settings.POST /funding-sources/{id}/micro-deposits