Dwolla signs users in with their Dwolla account — a payments identity, most often used by products that also move money through the platform.

## Copy the redirect URI

In the [Authdog console](https://console.authdog.com), select the project and environment, open **Authentication > Providers**, find **Dwolla**, and click **Enable**. Copy the redirect URI shown in the form:

```url
https://identity.authdog.com/api/v1/callback/<connectionId>
```

## Create the application

1. Open the [Dwolla Dashboard](https://dashboard.dwolla.com/applications) and open your application.
2. Add the redirect URI from Authdog to the **OAuth redirect URLs**.
3. Copy the **Key** and **Secret**.

## Configure Authdog

| Field | Value |
| --- | --- |
| **Client ID** | The Dwolla application **Key** |
| **Client Secret** | The Dwolla application **Secret** |

Save, then toggle the connection **active**.

## What Dwolla returns

Authdog requests the `accountinfofull` scope and reads the profile from `https://api.dwolla.com/users/me`.

The endpoint returns the account identifier and the profile information the `accountinfofull` scope permits.

Dwolla runs separate sandbox and production environments with separate credentials and hosts. This connector targets production.

## Test it

1. Open your environment's hosted sign-in page, or link to `https://identity.authdog.com/api/v1/signin/<connectionId>`.
2. Select the Dwolla button and complete the flow.
3. Confirm the user appears under **Users** in the console with a Dwolla identity linked.

## Troubleshooting

| Symptom | Cause |
| --- | --- |
| `access_denied` | Sandbox credentials used against production |
| Redirect or callback URL error | The URI registered with the provider does not match Authdog's exactly |
| Works in one environment only | Each environment has its own `connectionId`, and so its own redirect URI to register |

## Related

| Read | To learn how to |
| --- | --- |
| [Connectors](/docs/connectors) | Set up any other social provider |