Back to Podcast
Season 5Episode 251

Building the System of Record for Finance with Mural feat. Co-Founder Chris Fernandes

November 21, 2026
29m
1 Guest

Listen Now

About This Episode

In this episode of DevNTell, Narb interviews Chris Fernandes, Co-Founder and COO of Mural. Chris shares his background as a former forward deployed engineer at Palantir and explains how that experience in harmonizing disparate data sources led to building Mural, a financial infrastructure and compliance system of record platform. He discusses how Mural abstracts away the complexity of traditional fiat payment rails, stablecoins, regulatory compliance, and multi-model custody solutions behind a clean REST API and an MCP server. The conversation also explores the emerging agentic economy, highlighting Mural's investments in Know Your Agent (KYA) identity mapping and policy-engine control planes. Chris closes with advice for founders on maintaining a bias towards action and prioritizing hiring top talent.

Key Takeaways

1

Mural provides financial infrastructure and a compliance system of record via embedded fiat virtual accounts and stablecoin wallets, allowing developers to build global financial products without managing underlying regulatory and ledgering complexity.

2

Chris's experience as a forward deployed engineer at Palantir harmonizing disparate Fortune 500 data sources directly inspired Mural's architecture as an operating layer connecting fragmented local payment rails and stablecoin networks.

3

Developers can integrate quickly via Mural's REST API at developers.muralpay.com, leverage their MCP server to build prototypes in minutes or hours, and start easily with a new starter tier.

4

Mural supports three flexible custody models—end-user self-custodial (abstracting private keys with passkeys and email auth), customer custody (for licensed partners), and Mural custody (as a regulated US Money Services Business).

5

To support the growing agentic commerce space, Mural is building a Know Your Agent (KYA) identity layer and an infrastructure-level control plane policy engine to enforce granular spending limits, currencies, and approved counterparties.

Featured Guest

CF

Chris Fernandes

Co-Founder & COO @ Mural

Mural

Timestamps(click to jump)

Episode Transcript

Narb

GM, GM. Welcome to what's going to be another fantastic episode of DevNTell. So if you didn't know, DevNTell is a 30-minute podcast held every week allowing founders, hackers, and anyone in between the opportunity to come on the show and showcase what they built. And today I'm ecstatic to welcome Chris Fernandes, who is the co-founder and COO of Mural. So if you're not familiar, Mural is the compliance system of record you build on to move, store, and grow your money. So if you stick around for today's episode, you'll get to meet Chris, learn about the Mural platform, and how you can get started building with it today. All right, let's get into it.

Narb

GM, GM. Welcome to the show, Chris. I'm excited to have you on today, man.

Chris Fernandes

Yeah, thank you so much, Narb, for having me. Excited to be here.

Narb

Yeah, likewise, likewise. I'm excited for our audience to learn about Mural as well as yourself. The problems you guys are solving are very, very difficult ones for people who aren't familiar with the payments space, so hats off to you for doing that. But before we kind of get into all things Mural, would you like to give an introduction about yourself?

Chris Fernandes

Yeah, absolutely. Yeah, my name is Chris Fernandes, as you noted, co-founder and COO here at Mural. My background is in technology, kind of have been there since school. But anyways, going back, I originally grew up in Austin, Texas, did my undergrad out on the West Coast at Stanford, was at Palantir for quite a few years, and then now have been at Mural building since 2022.

Narb

Amazing, amazing. And yeah, I looked into your time at Palantir, and as far as I understand, you were a forward deployed engineer?

Chris Fernandes

That's right, that's right. Yeah, so there I was a forward deployed engineer, which is becoming certainly more of a common thing today. We actually at Mural run a forward deployed motion in which we embed directly with our customers to accelerate their product builds. But yeah, effectively was flying around the world kind of embedding with Fortune 500 companies and solving various big data integration and big data optimization challenges while I was there at Palantir.

Narb

Yeah, that's awesome, man. Just curious, how in your mind did that experience kind of lay the groundwork for you starting Mural?

Chris Fernandes

Yeah, yeah. So at Mural, a lot of what we're doing, and we'll get into really what we're building and more in a second, but a lot of what we're doing and building is connective tissue between the best of real-time local payment rails and systems—very different systems—and stablecoin rails, and kind of connecting those two things. Interestingly, at Palantir, even though I wasn't building in the payments or money movement space per se, a lot of what we were building were these complex integration challenges. Right? We'd come into a big Fortune 500 company—let's take a massive global shipping company—and they have 20 different data sources, none of them that speak to each other, so it's very hard to actually build on top of and solve problems and make decisions. And so what we would do is we'd connect to all these different data sources, and we would kind of harmonize the data and build an operating layer on top. And a lot of actually what we were doing there, although it was a different context—the example I just gave was optimizing shipping flows—here at Mural, it's a similar concept, right? We're connecting to all these different disparate payment systems, sources, ledgers, whatnot, and harmonizing them and building this operating layer that people can easily build financial products on top of.

Narb

Absolutely. And yeah, like I mentioned before, that kind of orchestration and connecting of the dots of all these different things that kind of make up just that magic process like you and I kind of feel when we send money over to a friend or something—there's actually a lot of complexity that kind of goes behind that. So, yeah, just kind of curious: what is Mural, I guess the pitch version of that, and kind of how did you guys go about solving all these complex connecting the dots?

Chris Fernandes

Great. So Mural in a nutshell is financial infrastructure for businesses building financial products. So what that actually means one layer deeper is the core infrastructure is effectively embedded accounts and all the associated services for moving, storing, or holding, and managing money. And when I say embedded accounts, I mean both fiat virtual accounts—so dollars, euros, pesos, real—and then also stablecoins. So we provision both kind of wallets and either real or virtual bank accounts so that people building products can provision those on behalf of their end users. And those use cases end up taking oftentimes different shapes. So just to kind of ground that in the context of Deel, who's one of our customers, right? They build a global payroll platform to pay employees and contractors all over the world. In our work with Deel, they're deploying accounts, which is both local fiat accounts and stablecoin wallets, for their employees throughout Latin America so that those employees can get paid in local currency but convert to digital dollars for holding their funds, which is important in certain markets where there's a lot of currency instability, at least as it relates to the dollar. So what we're providing in that situation, like with Deel, is the underlying compliance onboarding, the transaction monitoring, the sanctions screening, as well as actually opening up an account at one of our partner banks and the payment processing and conversion that runs through that account.

Narb

That's certainly a lot of heavy lifting, and I'm sure it came with a lot of technical challenges. As far as I understand, you're the technical counterpart to your co-founder, and I'm sure a lot of the early work you did kind of had you probably pulling out a lot of your hair just because of trying to figure out how to stay in the lane of falling under compliance and kind of building this tech stack out. Just curious, what were some of the bigger challenges and hurdles you kind of overcame while you were trying to do that?

Chris Fernandes

Yeah, yeah. So that is correct. Yeah, first off, my background again is in engineering as a software engineer, so even though I wear the COO hat, spent a lot of time building our stack and have contributed a lot to our codebase. My co-founder, Sinclair, also fortunately is technical as well, so I was able to kind of share the load with him in the beginning. But you know, as far as the challenges, I think that one way that I'm going to answer this is a little bit more on how we got there, because it was because of a lot of the challenges we were facing. And so the very first version of Mural, rather than being just the API and the infrastructure offering that it is today, was like a web application, in which we were actually selling directly to a business who was making payments and they would use our UI to make said payment. But the problem that we encountered was that having a real cohesive—again, we call this the compliance system of record underneath—that was reliable for storing money, reliable for sending and receiving money, properly performing the compliance and the transaction monitoring checks within one provider that we could plug into, it just didn't really exist. Right? So we were having to do this stitching together of many different financial institutions and providers and whatnot, and effectively we realized this is the product that we've built actually, is providing this operating layer on top of all the connections and the integrations that we've built. And that's also what we knew from our time at Palantir, was building really core lower-level infrastructure to solve these problems. And so to answer your question directly and to finish on that question, I think the challenge was always: how do you build a really simple set of primitives, or objects if you will, that developers who maybe don't know much about fintech or money movement or whatnot can understand without exposing them to the nuance that is all of the underlying payment systems and regulatory requirements and ledgering requirements, etc.? Because as a developer building a financial product, what do you care about? You have your user, you need to provision an account for them, you need a pay-in, you need a payout to a counterparty. So what we focused on is building those primitives very simply and abstracting away all the complexity underneath.

Narb

Yeah, and as a developer myself, that simplicity and being able to kind of pick something up like this and just get going right away without having to think about all the underlying nuances that you mentioned is pretty significant. And I guess on the topic of developers, as this is a developer show, this is a good segue into the front door, so to speak, into tapping into Mural. Could you speak to what APIs, SDKs, and other tools are available for developers to get started building?

Chris Fernandes

Absolutely. So our core product is our REST API. And so that is available and all the documentation is public at developers.muralpay.com. There you'll see—for any of those visiting that, I would start with just understanding those core primitives that I talked about to understand how the pieces fit together. And then the other place I always point people is to the MCP server. In today's post-AI world, building has never been—well, certainly more exciting than it is now—but also easier to get started. And so plugging into that MCP server, it really is as easy as describing the product or use case that you're trying to build and getting a prototype, I'm talking literally in the matter of minutes or hours. It's been really rewarding with our customers to see—we have a sales call or a scoping call, there's 'Hey, can we get access to the sandbox?', they plug in, and the next day they're like, 'Hey, we have our prototype built,' you know? And so yeah, our public API docs, it's all just available via REST, and the MCP server is where I would point people. And then for those who are looking to actually get started and have a real product that they're building or a company that they're building that relies on account infrastructure or money movement, getting in touch with me or our sales team will get you up and running quickly. I think importantly, and this is somewhat recent, we kind of started rolling out our starter tier, if you will, to where you can get started very easily for people building new companies or startups without a large financial commitment to kind of get started.

Narb

Amazing, amazing. And yes, all those resources will be in the description of the podcast, so if that is something that interests you, definitely take a poke around. And double clicking a little bit into the API itself, as I understand, you guys support a variety of different custody solutions from self-custodial to you custodying the funds. Just curious, what kind of played into that decision of supporting the wide array of options versus just going down one path?

Chris Fernandes

Yeah, so I think at Mural, we are purposefully building an API and infrastructure that is generic enough to solve varying kinds of use cases. Right? So I mentioned we have the Deel employee payroll use case. We work with a company like Opera, the browser, that pays tens of thousands of contributors to their site across the world just directly in stablecoins in a non-custodial manner. We work with a company like Exceso in Latin America who's bringing basically bodegas and merchants online as financial access points. And so we span across a variety of different use cases, and those use cases often require different custody models for varying reasons. It could be just a developer or a company is passionate about making sure that the users control their own funds in a self-custodial manner, or with bigger institutions or enterprises that actually want to offload that kind of responsibility to Mural to do the custody and management. So yeah, so we offer basically three custody solutions today. You can do what we call end-user custodial, so that's a self-custodial solution for the users of your product that you're building, in which all payments require explicit authentication from that end user—obviously we have abstracted away the private key nuance there to where we're talking passkeys and email-based auth, rather than needing the secret string or whatever. And then we have a customer custody solution, so for any of our customers that actually have their own licensing and the ability to custody funds on behalf of their users, they can use that model. And then we also have a Mural custody option, so we are a regulated money service business in the United States, we hold money transmission licenses, so in the jurisdictions that we hold licenses, we can be the custodian of the stablecoins in those settings.

Narb

Amazing. Yeah, and as a developer, whether you're on your own, doing a startup, or an enterprise, having those options is huge. So kudos to you guys for thinking two or three steps ahead there.

Chris Fernandes

Yeah, yeah. I think the exciting part is—sorry to cut you off—is regardless of the solution that you use, I think we've done a pretty good job in ensuring that the end-user experience for the products that you're building is always good. Do you know what I mean? So regardless of if they're custodying their own funds in a self-custodial model or it's Mural, it doesn't feel like a crypto app per se, you know what I mean, at least as it was a few years ago, right? It's just modern experiences for the end users, while making sure that we can choose the model that suits the job, especially as it relates to regulatory compliance and licensing.

Narb

Absolutely. Yeah, I think we're at a point now where the crypto side of it is kind of blending into infrastructure and people aren't really hyping it up in the spotlight as much as in previous years, which is great. That's exactly what it should be.

Chris Fernandes

Right, right. It's like I have some family members that are like, 'Oh yeah, Chris is working on his crypto company,' and I'm like, 'Listen, we are not a crypto company, you know? We are a financial infrastructure company, and we happen to use stablecoins to do a lot of our cross-border settlement because it's a super efficient and effective way of moving money. But we are not overly religious necessarily about oh, it has to be stablecoins or it has to be digital assets.' I think they have their purpose and they're great for a lot of the value transfer that's fast, that's cheap, that's transparent, but at the end of the day, I think the way that we continue to push out the new technology to the masses is abstracting away the nuance from that end user. And so that's been a massive focus of ours and continues to be.

Narb

This is the way, this is the way. And we kind of spoke about it a little bit here and there, but just this topic of AI. I think, of course, the majority of users on the internet today are humans, but I believe that AI agents are also going to be a big new customer base on the internet, whether that's for agentic commerce purposes or just assistants like the Muses and Dots and others of the world here. And it seems like you guys are kind of designing for that as well. Just curious how you guys are positioning Mural to support agentic use cases and AI agents actually moving money themselves, and kind of the control layer around them to make sure they stay in line, so to speak.

Chris Fernandes

Yeah, yeah. So at Mural, we certainly hold or share that thesis that looking forward even 6 months out, 12 months out, we're going to see a proliferation of agents acting on behalf of users or humans, specifically in the context of financial use cases. So whether that's your agent making a recurring remittance payment to a family member that you have in Mexico, or whether that's buying something as simple as buying a flight, we're going to continue to see this, right? And the challenge is: how do you prevent these agents from doing things that they shouldn't be doing? That's maybe one part of it, more on the authorization side. And then there's also the identity side. It's like: who is actually making this action on this account, right? And so two areas that we're investing in at Mural is that KYA layer—so how do you actually know the identity of an agent that's making an action?—and then also what I'll call the control plane layer. So we're building a policy engine, if you will, that is directly linked to the account and the credential that the agent is using to access that account, so that our users can basically set granular controls and permissions on top of that. So that's things like: how much money can they spend in a single point in time? What are aggregate payment limits? What currencies do they have the ability to use? What counterparties can they send to? As we all know, these agents can go rogue and do things that you don't tell them to do, right? And so our viewpoint is for this to really work in this world that is inevitably coming—which again I believe to be more agents making transactions than humans is where we're heading—the KYA and agentic control layer needs to be linked and embedded at the infrastructure layer, at the account layer, you know? One interesting thing that I actually just saw literally yesterday was Citibank came out and they changed their terms of service to basically make users liable for any actions that an agent takes on their account, or if the agent leaks the credentials to their account and a human actually steals those, but it was the result of an agent, the human is still liable. And while I maybe don't disagree that the human should be liable for some aspects of maintaining account security, part of the reason they're doing that, right, is they don't have the control layer built on their account infrastructure to be able to responsibly manage these agent actions. So the easy thing to do is say, 'Okay, this isn't our problem, and if anything happens bad, it's your fault,' you know? And so I think there's a really interesting implicit opportunity there, that is building this control layer and this KYA layer from first principles, right? So yeah, we're pretty excited about it, and we're super interested also, for anyone listening, anyone building in this space that is agentic-first user experiences, we would love to have you build on Mural because it's still nascent, right, in terms of how these things are going, and so a lot of the stuff that we are building is with design partners.

Narb

Amazing. Yeah, it's certainly a very big ocean of opportunity in this particular sector, from banks like you mentioned saying 'It's your problem, you messed up, it's your problem,' to merchants like Amazon and some other big ones kind of blocking agents from being able to purchase anything altogether. So there's lots of different pieces that go into making all that come to fruition, and certainly the control layer is one of them, and another one is that identity layer. You mentioned KYA, but I imagine where this will kind of land at least in the near term is this hybrid model of an agent's identity kind of being tied to your identity or the payment source. Whether or not agents get their own identity like a business or whatnot, who knows, but I think it'll land at that intersection, and it sounds like that's where you guys are thinking too.

Chris Fernandes

For sure, for sure. Yeah, on that last part, there's the interesting hypothetical of at what point does the agent actually become its own identity, not linked to a human, completely acting on behalf of itself? And that is a fun one to noodle on and think about. But yeah, I agree that for the time being, the way that we're viewing it and building it is core Know Your Customer and Know Your Business will always be done on the business or the individual that we are provisioning the account for, and agents are linked to those entities—so the individual or business. However, especially in a world where people are running multiple agents, right—you might have your Muse doing something and your Instinct doing something and whatnot—there does need to be a mapping layer to understand who is making which action, right? So if Mural provisions an account for you and you're making payments, whether it's you in some UI or dashboard making a payment, or it's an API key that you're running from your local machine to make a payment, or it's an agent within the context of another app, there's a layering that needs to happen that's like, 'Okay, cool, we understand that actions on this account are associated with Chris Fernandes. However, from a monitoring—going back to the compliance system of record piece too—for a monitoring and auditing and permission level, we need to know that this call was Agent A, this call was Agent B, so that you can monitor and also turn off—oh, Agent A is going rogue, we need to be able to control this.' So anyways, totally agree with you that right now there is a linking still with existing compliance controls and frameworks, and there has to be, but providing the auth layer to know who is doing what action is the input to then be able to say what actions can they do. And so that's kind of how we're building.

Narb

Beauty. And yeah, really exciting times and very interested to see how different people approach the problem and present their own solutions. Excellent, excellent. Exciting times ahead, it sounds like for sure. And as we're coming to time, I'm always curious to pick the brains of founders and see how they can provide some sage advice for builders and potential founders today. So I guess from all your experience going through the ups and downs of co-founding Mural and perhaps even your time at Palantir, is there any advice you'd be willing to give people watching today who might be on the cusp of starting a company or proceeding with their own project?

Chris Fernandes

Wow, so much. We could do a whole episode on just that, but to keep it tight to just a couple minutes, two things come top of mind for me immediately. We at Mural, a very big part of our culture is this bias towards action mentality, especially in today's agentic world—it's so easy to just go build the thing, you know? Just go ship it, rather than putting together the scoping doc that you have five people review before... just build, you know? And I think that especially in the early days, you're going to be doing a lot of things and a lot of the game is trying things and seeing what happens and seeing what sticks. And so just build and bias towards action, and get it out there and collect data and then refine. And then the second thing, less so on just the building side of things, is just hiring and bringing on great people is just so important and is probably my most important job as a founder, right? My job is to hire people that are better and smarter than me, and that is a really hard job. And it takes a lot of time and resources that you have to devote to really finding great people and entrusting them with responsibility, but I think that's really how you win—is it's all about the people. So for any of the new founders out there, you're only going to be able to do so much, so focus on finding those really great people that are excited about what you're building and partner with them.

Narb

Beautifully said. Yes, yeah, absolutely, couldn't agree more. And I think that's a wonderful way to cap things off here. Chris, thank you again so much for taking the time out of your busy day to come share the story behind Mural, your origin story as well, and wishing you guys nothing but the best of luck as you continue to evolve the platform from here on out.

Chris Fernandes

I very much appreciate it, Narb. It was great to meet you.

Narb

Yeah, likewise, likewise. And again, for folks who are interested in getting started or learning more about Mural, all those resources will be in the description of the podcast below. And quick ask, Chris: if people are keen to reach out, what's the best way for them to get in touch with you?

Chris Fernandes

Reach out to me directly. Yeah, my email is chris@muralpay.com. You can ping me direct, and then like I said, check out developers.muralpay.com for information about our product and our infrastructure. And then we're also super active on LinkedIn, so I would check out our LinkedIn page for both me and my co-founder Sinclair. So yeah, hit me up directly.

Narb

Beauty. There you go. And with that, I just want to thank everybody again for tuning in today. Wish you all a happy Friday, happy weekend wherever you may be, and we will catch you back here next week for another great episode of DevNTell. Until then, have a good one, folks. Cheers.

Listen On

Resources & Links

Share This Episode

Share on X

Watch Episodes Live!

Subscribe to our event calendar and never miss a live episode.

View Event Calendar