Skip to content
Dwolla authentication strategy for Passport and Node.js.
JavaScript Makefile
Latest commit c3bd231 Aug 24, 2015 @jaredhanson Bump version to 1.0.0.
Failed to load latest commit information.
examples/login Initial commit. Dec 6, 2011
lib Depend on passport-oauth2, remove pkginfo. Aug 24, 2015
test Depend on passport-oauth2, remove pkginfo. Aug 24, 2015
.gitignore Update ignore files. Jan 24, 2013
.travis.yml Update vows, Travis CI config. Aug 24, 2015
Makefile Update project metadata. Jan 24, 2013
package.json Bump version to 1.0.0. Aug 24, 2015


Passport strategy for authenticating with Dwolla using the OAuth 2.0 API.

This module lets you authenticate using Dwolla in your Node.js applications. By plugging into Passport, Dwolla authentication can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express.


$ npm install passport-dwolla


Configure Strategy

The Dwolla authentication strategy authenticates users using a Dwolla account and OAuth 2.0 tokens. The strategy requires a verify callback, which accepts these credentials and calls done providing a user, as well as options specifying a client ID, client secret, and callback URL.

passport.use(new DwollaStrategy({
    clientID: DWOLLA_KEY,
    clientSecret: DWOLLA_SECRET,
    callbackURL: ""
  function(accessToken, refreshToken, profile, done) {
    User.findOrCreate({ dwollaId: }, function (err, user) {
      return done(err, user);

Authenticate Requests

Use passport.authenticate(), specifying the 'dwolla' strategy, to authenticate requests.

For example, as route middleware in an Express application:

  passport.authenticate('dwolla', { scope: 'AccountInfoFull' }));

  passport.authenticate('dwolla', { failureRedirect: '/login' }),
  function(req, res) {
    // Successful authentication, redirect home.


For a complete, working example, refer to the login example.


$ npm install --dev
$ make test

Build Status



The MIT License

Copyright (c) 2011-2013 Jared Hanson <>

Something went wrong with that request. Please try again.