Here at Dwolla, we want to make sending and receiving payments easier and more accessible for you to build on top of our platform and into your own applications.
We’ve recently released improved recurring payments functionality in Dwolla.com, and with that comes improved recurring payments functionality in our API. You now have the ability to leverage one-time scheduled or recurring payments by building with our Scheduled Payment API.
Features of scheduled, recurring payments:
- Set up a bank-sourced payment for a time and date in the future
- Establish the frequency of the payment: weekly, every two weeks, 1st and 15th of the month, or monthly
- Determine a date or time for completion of payments by making a one-time payment, ending a recurring payment after a certain number of payments, or ending it on a specific date
- Payments can be scheduled for up to three years in the future
For an integration or services that require regular recurring payments, this new feature is perfect—think CSAs, landlords, nonprofit donations, or membership fees. No money moves until the scheduleDate you’ve provided.
Take a look at the example below. In this scenario, we are going to send $9.95 to someMerchant@dwolla.com every other week on Mondays.
In this example, the Dwolla Account is connected to a FiSync-enabled BBVA Compass account, so the $9.95 will move in real time every other week starting 5-20-2015. In a matter of seconds, the recipient will have access to their funds. Pretty slick!
Additional OAuth scope: Scheduled
The OAuth scope, Scheduled, allows your users to give your application permission to create, edit, and delete scheduled payments on their behalf. You’ll need to add Scheduled to your app’s permissions, as well as an authorization request URL.
Get busy building
With the added functionality in our new recurring payments feature, the integration options are far more powerful. If you’re looking for inspiration, check out our sample Ruby on Rails app that implements scheduled payments.