The ability to create recurring payments via the API has been, without a doubt, one of the most requested features over the past few years. Today, we’re excited to announce that recurring payments are finally here, in the form of Scheduled Payments. It’s Christmas in April.
Scheduled Payments allow you to schedule a bank sourced payment for some time in the future. They can be one-time or recurring. When you create a scheduled payment, no money is transferred until the
scheduleDate you provided. This is perfect for subscriptions and other payments that need to happen on a regular basis, like rent or membership fees. Read more about Scheduled Payments in our API docs.
Let's say I want to send $9.95 to
someMerchant@dwolla.com every other week on Mondays. I'd make an API call like this:
Authorization: Bearer 10nNPKqaTfBy3qpe7Xnu+zlacHhjlct9cBgHN0NBWCuGkHxluA
"notes": "Biweekly subscription charge",
It happens to be that I've connected a FiSync-enabled BBVA Compass account, so every other week starting 5-20-2015, $9.95 will be sent and made available to the recipient in real time.
Options for recurring payments are quite flexible. You can create a recurring payment that pays weekly, monthly, daily, every week on Tuesdays and Fridays, every 12th and 18th and 26th each month.
Every week on Tuesdays and Fridays:
On the 12th, 18th, and 26th of every month, until the year ends:
New OAuth scope: Scheduled
We’ve added a new OAuth scope,
Scheduled so your users can give your application permission to create, edit, and delete scheduled payments on their behalf. Before you get started, remember to add Scheduled to your app’s permissions and include Scheduled in your OAuth authorization request URL.
Give it a try
We’ve built a sample Ruby on Rails app that implements scheduled payments. Check it out!
Our node.js, ruby, PHP, and python libraries have been updated to support scheduled payments.
Feedback, comments, need help integrating? We’re always happy to help out. Reply below.