Dwolla.js - Bank verification for developers in just a few lines of code

@tommyrva - I think of it this way. Our network is still behind our platform and white label customers can pick and choose how they want to use the technology. Our white label customers may not all take full advantage of our network and they may simply want ACH to ACH transfers between bank accounts. Other customers, have an entire balance infrastructure and member to member payments that's driven entirely by our network. Here are 2 examples. 1. A company building an entirely new mobile wallet. It has it's own products, and users. It needs a way to load/unload the wallets and a way to actually maintain balances behind the scenes without all of the technical headache of starting from scratch. They're using our network to manage all of this and our software platform to manage transactions. The 2 get tied together as part of the white label package that solves the problem they want to solve. 2. A company that needs to pull in payments 5-10 times per month from hundreds of people and then disperse those payments, take their cut, and send the funds directly to another party. They probably don't ever want to use Dwolla's network to hold funds somewhere, but they'll use our software platform to manage the funds flow between bank accounts. What we find is that how this all gets wrapped up into our customers final app just depends on what product they want to provide. More often than not our benefit is that we help our early stage customers get to market faster, at a much lower cost than building it themselves. In our later stage customers we're helping them solve operational inefficiencies. There are a lot of potential applications but these are things we're seeing a lot of. In any of these scenarios. Anytime you need to authorize a bank account it's good to be able to do it quickly without eating engineering resources up for months!

@bpmilne I think that's fantastic. Amazing complexity to this stuff that folks don't understand, probably 5x more complicated than the card payment infrastructure. Huge opportunity with very few if any existing options for folks building tech that requires it.

@melissamonteee We are excited about working with Lenny!! Cheers

@aaran_mcguire Bank credentials are provided through the Dwolla hosted IAV experience to our technology provider. This offloads the risk of capturing sensitive bank information for applications building on Dwolla's White Label API, where we require bank verification before we'll move funds from the account.

@yozapli There absolutely are opportunities for startups, please email bizdev@dwolla.com and they can help you out! Thanks!

@yozapli We do hear a lot from startups and we love working with companies to get off the ground. What features that are provided in a ~$2,5K a month package would include a lot of services that would likely save 6+ months of development/legal time for a company getting off the ground. In same cases probably more... To get Dwolla started it took me 2+ years just to find the first bank to work with! I'm just making the assumption someone else could do it in a lot less time than I did when I say 6 months.

@arush - The biggest difference is that this is not a standalone auth service that Dwolla sells. Dwolla.js is designed to make authorization easy for the purpose of transferring money as a part of Dwolla's white label product. - https://www.dwolla.com/white-label For those using our white label services Dwolla.js makes authorization very simple.