June 2019 Updates
As we progress towards our mission of building the ideal platform to move money, we continually introduce ways to showcase our customers’ businesses and brands.
By listening to the needs of our API clients, we are able to evolve our offerings to better support their needs.
Check out our updates from the Month of June:
bankAccountType - Loan Account:
Many Dwolla clients have use cases where Customers may need to move money from one bank account to a loan account for the purpose of loan payoffs. Now, in the Dwolla API, you can add a loan account funding source. This funding source can also be assigned on transactions for Loan Account Credits. To learn more about this feature and how to enable it in Sandbox, contact our team.
Token Management Support: dwolla-v2-node (v3.0+)
Access Tokens expire after 60 minutes, requiring developers to retrieve a new token when their current token expires. dwolla-v2-node (v3.0+) introduces new request methods on the client object itself that take care of managing tokens for you. Check it out!
Beta Release: Kotlin/Java SDK
Our Kotlin/Java SDK is now in beta. We’ve added some higher-level methods in addition to the lower-level GET, POST and DELETE methods found in our existing SDKs. These methods perform common tasks like fetching resources upon creation and bake-in best practices like idempotency keys. Most importantly, their type signatures specify the parameters required for each request. Check it out!
Each month our engineering team produces technical content for the engineering community. These could be product updates, as well as some infrastructure improvements Dwolla has made for others to learn how to implement them within their own organizations.
Protecting Stored User Passwords
Highlights top methods for password hashing
Implementing a CMS in 3 Days
Highlights pros / cons of using Netlify CMS
Caching with CloudFlare Workers
Highlights platform improvements with Cloudflare Workers
Dwolla systems continue to maintain excellent uptime in June, exceeding our uptime commitment of 99.9% uptime.
We are actively working on making an update for customers moving funds between two accounts that are owned by the same individual, typically referred to as a Me-to-Me funds flow. Currently, two API calls would be required for that to work. With this new update, the same functionality can be performed with only one API call. Stay tuned for more details.