> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/dwolla.md).

# 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](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), 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]`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/connector_configs/toml/sandbox.toml#L2441-L2443) 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](#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](https://app.hyperswitch.io/) 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`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/dwolla/transformers.rs#L550-L574)). 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`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/dwolla/transformers.rs#L519-L546); the mapping to an outcome is at [`TryFrom<DwollaWebhookDetails> for IncomingWebhookEvent`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/dwolla/transformers.rs#L576-L608). 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()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/dwolla.rs#L888-L915). 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](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/dwolla.rs) and [Dwolla transformers](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/dwolla/transformers.rs).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/dwolla.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.