Blog

Processing XML in Go has traditionally involved repetitive code, runtime type assertions, and complex validation logic. Modern Go applications demand better: type safety, maintainability, and performance. I want to explore how Moov’s wire20022 library demonstrates a comprehensive approach to XML processing using Go generics, embedded structs, factory patterns, and idiomatic interfaces.

Let’s talk about a pain point. You’ve built a solid product. You’re ready to add users. And then…onboarding.

Now that 2024 is a wrap, it’s incredible to look back at all we’ve accomplished. Last year was about pushing boundaries, listening to our users, and delivering tools and features that make financial services more accessible and intuitive. From new payment capabilities to stunning new user interfaces, we’ve shipped features that empower businesses to move billions of dollars.

When you open a new bank account, there’s usually one dominant emotion driving that decision: frustration. You’re fed up with your current financial institution. Maybe your account was mishandled, or you didn’t like the fees, or perhaps your bank just wasn’t meeting your needs. So, you decide to open a new account somewhere else.

Instant is becoming the new standard for virtually everything—including money movement. And it’s not just a matter of convenience. The ability to transfer and access funds in near-real time, 24/7/365, can solve cash flow challenges and open up new payments use cases and business models.

Payments are mission-critical for SaaS companies, and their customers expect multiple payment options. But offering more than one payment rail means orchestrating multiple systems from numerous vendors. This requires significant engineering resources—which many businesses can’t spare.

Moving money is moving data. So, when Moov enables payments across all the major rails, what we’re really doing is creating a single source of truth for all that data. Receiving, sending, and storing; through card, ACH, RTP, and most everything else—it’s all in there.

Late payments are a real problem—for borrowers, lenders, service providers, and the entire economy. The World Bank estimates that they cost the global economy more than $40 billion a year. There are a lot of reasons for late or missed payments—from cash flow issues, inaccurate or confusing invoicing, or just forgetting a due date.

You’ll never hear an accountant (or an engineer, for that matter) say, “That’s probably close enough.” When you’re dealing with financial transactions—or building a system to record and handle them—precision matters. If you keep an eye on Moov’s changelog—where we post new products, features, and improvements—you might’ve noticed updates to the precision of our ledger. We upgraded transfers, wallet transactions, and wallet endpoints to handle additional decimal places: up to nine decimal places to be exact (because, again, precision matters).

We’re always looking for ways to make it quick and easy to embed new payments functionality within our customers’ user experiences. Moov Drops are a perfect example of this. These pre-built UI components can be securely dropped (thus the name) into our customers’ payments experiences with very little developer lift.

At Moov, we believe problem-solving should take priority over shiny new technology. While we love breaking the payments mold (in 2022, we became the only cloud-native acquiring payments Processor), we’re also laser-focused on getting the details right—down to the tiniest transactions.

Statement descriptors are the text that describe transactions presented to us by our digital banking feeds (or paper statements) so that we can recognize them. Setting thoughtful and clear statement descriptors not only improves user experience through ease of recognition but can also reduce disputes.

If you’re building a SaaS platform or any sort of business where customers need to pay online, the question of how to accept card payments is a familiar one. With this in mind, we’re excited to announce that Moov has launched card acceptance.

I learned a valuable lesson as a young product manager years ago that transitioning your product from a cost center to a profit center for your customers changes the dynamic of your relationship with them. It seems obvious, but it’s often lost on software and service providers that their product offering impacts the business model for its customers. That’s why at Moov, we’re focused on ways to help our customers grow their business with new revenue streams and simplifying the workflows of money movement.

Moov’s mission is to make it easy for applications to accept, store, and disburse money. Transfers in Moov are instructions to move money between source A and destination B. But what do you do when you need to accept payment from one source and disburse it to multiple destinations? How do you collect a fee from one or more of those participants? How do you make sense of all of the individual money movements from a reporting and reconciliation standpoint? And how can you chain these actions together?

If you’ve ever created an onboarding flow, you know how complicated it can get. It seems simple at first, but handling every failure state is tedious. Yet designing a solution for every scenario and edge case is paramount to a great user experience.

Even though we push to production every day at Moov, there’s nothing quite like publishing the changelog and seeing the complete list of what’s gone out. It feels great to start the new year strong—shipping new features that will help you work towards your roadmap goals and start building delightful payment experiences. In today’s round-up, we highlight a few new additions to the Moov platform.

Whether you’re a developer, product manager, or just a curious builder exploring our money movement platform, one thing is critical as you get going: the ability to play, interact, and test—quickly. You might find yourself in “guess and check” mode and need to see how the thing you’re building interacts with our services. This is the beauty of our new test mode—you can pound the same operation over and over until things are just right—all without sending any real money.