Dwolla

Connect Dwolla through Hyperswitch.

Dwolla supports ACH direct debit in the sandbox, with refunds and automatic capture. Payment and refund webhook flows are declared.

To connect Dwolla to your Hyperswitch account, follow Activate a connector on Hyperswitch, then return here for what Dwolla supports.

Status and capabilities

Integration status: sandbox

Category: payment gateway

Webhook flows: payments, refunds

Payment method	Type	Mandates	Refunds	Capture methods	Countries	Currencies
bank debit	ACH Direct Debit	not supported	supported	automatic, sequential automatic	USA	USD

Authentication

Activation needs three values, not two. [dwolla.connector_auth.BodyKey] supplies the first two labels and the connector metadata supplies the third:

Field	Required
Client ID	yes
Client Secret	yes
Funding Source ID	yes, from dwolla.metadata.merchant_funding_source

If you take webhooks, also set Source verification key. It is not an authentication credential; it is the HMAC key the webhook check runs on, from dwolla.connector_webhook_details. See Webhooks.

Before you start

1. Obtain your Client ID, Client Secret and Funding Source ID from Dwolla.

2. Sign in to the Hyperswitch control center and open Dwolla, which is offered in the connector list.

3. Enter all three during connector activation. Activation will not complete without the funding source ID.

4. If you take webhooks, enter your Dwolla webhook secret in Source verification key.

Webhooks

Dwolla's event enum recognizes 21 topic wire values, plus an Unknown fallback that any unrecognized topic resolves to (DwollaWebhookEventType). Only six of the recognized topics change a payment or refund. Everything else resolves to EventNotSupported and applies no update.

What a handled event means depends on whether the callback belongs to a refund, which the connector decides from the correlation id: an id beginning refund_ makes it a refund event.

Topic	On a payment	On a refund
customer_transfer_created, customer_bank_transfer_created	Payment is processing	No update
customer_transfer_completed, customer_bank_transfer_completed	Payment succeeds	Refund succeeds
customer_transfer_failed, customer_bank_transfer_failed	Payment fails	Refund fails

The topic strings above are what Dwolla sends on the wire, matched in From<&str> for DwollaWebhookEventType; the mapping to an outcome is at TryFrom<DwollaWebhookDetails> for IncomingWebhookEvent. The other fifteen recognized topics, the customer and funding-source and microdeposit events, parse but do nothing, as does the Unknown fallback for unrecognized topics.

A callback that arrives with no correlation id at all is dropped before the topic is even read: the handler returns EventNotSupported regardless of which event it was. Payments and refunds started through Hyperswitch carry one, but a transfer created directly in Dwolla may not, and no such callback will update a payment.

Callbacks are verified with a real HMAC-SHA256 over the request body, keyed on your Source verification key, at verify_webhook_source(). A callback that fails the check is rejected.

Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch 502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5. See Dwolla connector source and Dwolla transformers.