Our commitment to creating a diverse culture in fintech development.
fintech_devcon is the first-ever fintech developer conference. Our vision is to bring together like-minded developers and increase the voices heard throughout the financial technology space. We’re committed to improving access, participation, and engagement for all people, regardless of identity or background. We created our scholarship to support this commitment, and we’re excited to extend our sponsorship to five individuals.
After announcing fintech_devcon earlier this year, we’ve been blown away by the positive response. Not only are developers eager to finally attend a conference dedicated to them, but it’s exciting to see that people are ready for in-person events again. While there’s certainly a draw for a chance to finally dust off your suitcase and pack clothes other than sweatpants, we’d also like to provide a business case for attending fintech_devcon.
The number one question I get about regarding the Moov open source libraries is, “How do these fit into my application stack?” In this post, we’ll set out to answer this question once and for all. Before we talk specifically about our open source projects, it’s essential to look more broadly at how most companies interact with the banking system programmatically.
The fintech developer community has exploded. While the growth has been happening for a while, 2020 saw an exponential expansion. This explosion has created a massive demand for education and brought a new wave of developers into the space. It’s time they all met.
Last week we hosted two conversations for the Moov community. The famous Cokie Hasiotis from Fintech Today joined us for happy hour. For our first Moov Global Community conversation, we spoke with Simon Taylor of 11:FS.
We recently welcomed Zach Bruhnke the CEO/Janitor at HMBradley to be a speaker at our Moov weekly happy hour. Zach is a longtime member of the Moov community and fintech veteran. He spoke on a broad range of topics in the challenger bank space, and his ideas were so good we decided to write them up to share with the community.
How and when to use the Moov ACH library The Moov team was founded by industry veterans who have been dealing with legacy technology for decades. It’s this experience that led to the creation of our open source projects like ACH. What we noticed was that teams across the financial industry are consistently solving the same problem, often causing huge headaches. The information around how to solve these problems is freely available but it’s buried in lengthy manuals and layers upon layers of insider jargon.
The recap This month marked the first meetings of the Moov ACH and ICL working groups. Our first of many ongoing monthly meetings where community members come together and discuss how we can improve our open source projects. These meetings started a few weeks ago when one community member asked a question about mobile check capture. What resulted was a lengthy discussion and, finally, a suggestion to host a call.
Getting started Building ACH files is no small task. The sheer number of fields required is enough to make your head spin. This tutorial will use our Node SDK and a CSV of mock employee payroll data to generate a Nacha compliant PPD ACH file.
In Part 1 we covered how to update our README and GitHub Pages documentation. In this article, we’ll map out how to quickly and easily suggest changes to our API documentation.
The documentation for our open source projects is here to serve you, the community. We’re always interested in feedback from those using our open source libraries and incredibly thankful to anyone willing to contribute to them. In this article, we’ll map out how to quickly and easily suggest changes to our documentation.
