The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Stablecoins Beyond the Hype: Building Africa's Cross-Border Payment Infrastructure | Mercy Emmanuel

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

Mercy Emmanuel of Flutterwave tells builders that customers do not care which stablecoin or chain is used; they want money to arrive predictably in the right currency. Using a Lagos retailer paying a supplier in Kenya, she lists what a payment rail needs: compliance checks, collection, executable exchange rates, liquidity partners and pre-funding for instant transfers. She says founders must think like bankers.

Not by We Them Media Channel: Web3Bridge. Published Monday 26 October 2026.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:00 A: Hi everyone, I am Mercy Emmanuel. I'm currently the stablecoin and blockchain vertical lead at Flutterwave. I hope you all know who Flutterwave is. Flutterwave is Nigeria's foremost payments institution, Africa's foremost payments institution, to be honest. And I currently lead our foray into the blockchain and stablecoin ecosystem. That being said, I'm talking to, talking to you today about building practical payment rails for Africa's cross-border economy. So I'm going to be focusing on 3 things. I am going to laser my- or narrow my focus to 3 things. One, practical payment rails. I am going to talk to you about actual what do you need to do to build a payments rail. If you are here today and you are trying to build a payment product, I'm going to tell you exactly what you need to do. The second thing is Africa's cross-border, meaning the focus of the kind of payments rail that you are building is solving for cross-border movements. So I'm going to be telling you exactly how to build a payments rail that solves for Africa's cross-border business, cross-border movements, and specifically for Africa. Right? Cross-border movement specifically in Africa. Okay. So now that we are clear on these 3 things, let me go into the conversation. The first thing I want to tell you is your customer does not care about stablecoins. Right. That's the first thing I want to tell you. If you are building a payment rail for cross-border movement, the first thing you should know Your customer doesn't really always care about stablecoin. And this might sound like heresy in a Web3 conference, to be honest, because what do I mean your customer doesn't care about stablecoins? What I mean is when your customer is thinking about moving money across borders using you as a payment rail, their question is not, is it USDT? Is it USDC? Is it Polygon? Is it Ethereum blockchain? Is it- no. Their question is, how do I move money from where my money is today in my bank account, in my Momo wallet, to where I want it to go through? So to this recipient's bank account or mobile money wallet in the country that that person is, in the currency that the recipient is expecting to receive in? That's what they're trying to solve for. They're trying to solve for a predictable outcome, nothing more, nothing less. And so your product must be designed to answer that question or those questions, right? If you're building a product today and you're building for cross-border movements, the questions are, how much is leaving my account? How much will the person receive? When will it arrive? And if something goes wrong in this movement, who fixes it? That's the question, and that's what you're supposed to understand, and that's what you're supposed to be building. When you are building for a business, right, you are building as a business builder, your thinking should start with a repeatable transaction. So if you're trying to build a payment rail, like I mentioned, I'm going to tell you exactly how to build a payment rail. Your thinking should be Who is paying whom? First question, who is paying whom? Where are they paying each other? What countries? Next question will be, how often does this payment happen? Is this repeatable? This is a one-time thing. It's something that happens once in a blue moon. It happens every day. Is it seasonal? Is it a repeatable action? Right? How painful is the experience today? The way that they are solving for this movement today, how are they doing it and how painful is it? If what they are doing today does not cost them a lot of pain, the chances that they want to adopt a new method to do it is very slim. So you have to quantify it. The movement that they are doing today, how are they solving for their problems and how painful is it? And then when we quantify what the pain is, is now who feels the pain strongly enough to want to pay for it? These are the questions you need to answer as a business builder. You need to ask yourself these questions truly, and when you have answers to these questions, you have just started thinking about a payment trail. Okay, who is paying whom? Where are they paying each other? What is the experience today? How painful is it? And who wants to pay for the relief of that pain, right? So your answer cannot be, I'm trying to build cross-border payments for Africa. No, Africa is not just one corridor. Africa is a mixture of 42 minimum different corridors, right? We have about 42 currencies. Yeah, about- so it's a minimum of 42 different corridors. Payment is not just one, one, one job. Payment is a mixture of multiple things. So you need to think really deeply and answer that question very, very quickly, right? So I'm going to- like I mentioned, the payment starts with one possible corridor. Africa is not just one corridor, right? So when you are thinking about your business, the first test is, can you name the customer? Can you name the frequency of transaction that they are- that they're doing? Can you identify the pain? Who is willing to pay for that pain to be eased, and what is the path to getting into that market? Those are the first things that you need to understand. It's when you have answered these questions that you are beginning to start a payments- a payment business. If you don't have answers to these questions, then what you have is an idea, an infrastructure idea, right? And that's not bad. You just have to refine it a little bit more. You have to narrow your gaze to answer these questions very, very clean. All right, so if a Lagos retailer- so I, I, who's my customer in this instance? My customer here is a Lagos retailer who wants to pay a supplier in Kenya. That's it. I am a Lagos business who sells textile clothes in Nigeria. I source my material from Kenya. It's repeatable because I have customers that come to my business every day. And I want to be able to pay my customer in Kenya every time that I need to buy supplies. We have answered these questions. Paying my customer in Kenya today is painful because every time I need to do that, if I'm going to go to a bank, it's going to take T plus something, T plus 2, T plus 3, before it gets to my person in Kenya. And sometimes what that means for me is after I have locked down these goods, right, for this price, somebody who has a better, faster way to pay can come and pick up the goods before my payments get stale. And so sometimes I would lose my deals. We have found the pain. It also can be very expensive for me to do these payments. If I'm going to the bank, sometimes it fails, the cost is too high, and the supplier doesn't always get the money that they expect- I expect them to get. Found pain. Who is willing to pay for it? Me. My business needs this to move, right, so that my business continues to expand and I can continue to sell Kenyan source materials in Nigeria. We've answered that question. So how do I solve for it, right? As I'm building a payment business, I have my Lagos retailer who wants to settle their Kenyan supplier, and my Kenyan supplier who wants to receive KES, doesn't want anything else. He wants to receive KES at a particular time. He wants certainty and he wants his local currency. This is the part where stablecoins comes in. When you have this orchestration, and we have looked through what the pains are, we have just explained that banks with the banking, it has XYZ problems. Stablecoin comes in here at the middle layer. At the part where you want to do the orchestration from Nigeria to Kenya, that is the corridor problem, and that is the part that stablecoin sits in. But the corridor problem is not only a stablecoin- only stablecoins alone cannot just fix that corridor problem. Multiple things need to happen, plus the stablecoins, because it helps with faster money movement, right? We're using stablecoins here to bridge the gap so that it goes from NGN to USDT, USDC, CRO, USD, and from that to KAS. Because with that movement, it bridges the gap. But that's not the only thing that happens here. Multiple things have to happen at once. I have to be able to identify, does the customer- is the customer eligible for this action? Meaning, do I have the KYC, KYB, and compliance goal for this customer to do this action? That's the first thing I want to think about. Second thing is, do I have access to receive this person's local currency, this MGN that they have in their local bank accounts or in their Momo or anywhere they have it? Am I able to receive it and collect it? What is the collection engine for that? The next bit is, when I collect it How do I sell it and swap it for USDT, USDC, or USD? Because we have agreed now that that helps in solving the time, right? Where is the FX and liquidity coming from? Do I have a partner, or do I have an FX partner? Do I have an OTC desk? Do I have a bank? Do I have- who is ready to receive this fund for me at a particular price? Right, and give it to me at a particular time. Who is ready to do that? Do they have the licenses to do so? Are they- is that person that we're able to do that compliant, right? Am I interacting with a compliant party? When I get that USDC, USDC, and I want to convert it to KES or send it, pay it out to KES, right, when I've done the conversion, I've got in my liquidity FX, I've moved from USD to USDC, my time is up already. Mad. I moved from that to that, right? And so the next question is, how do I do the payouts? Who is going to do the payout? And is that person compliant enough to do said payouts, right? And so when I answer that question, I now answer, is there a way to identify the payments from end to end so that support reconciliation can do their job? Can say, if customer comes and says, ah, I sent this money, no go. Can support check. Is there a transfer ID? You need to have this working to be able to solve for this movement. And all of these- the beautiful thing about all of this is that in the big trend, 2026, that we are in today, all of these questions are already solved. All of them. People have built the different pieces of the divide. Somebody has built how to make your customers eligible. You have all the KYC platforms, you have, um, Veriff, some, some, all of them, right? You have all the KYC platforms that can help you identify that customer and make sure that customer is eligible, right? To check against the OFAC list, to check again that. So the first thing you want to do is have that partnership. Then you want to be sure who am I partnering with to collect these local payments? This is where you have- again, other people have built these things. This is where you have partners like Flutterwave, right, who can help you. Traditional Flutterwave business is to collect, collect and pay out traditionally, even without the crypto part of it. This is where you have all those other partners that can help you collect, collect local naira. You hold local naira somewhere. Then the next bit is who does the transfer, the FX. Who can I give? One thing I've seen sometimes is some people do, uh, you know, you go to your exchange, you go to an exchange, or you go to Google and you use that as the rate you show your customer. That's, that's a little bit crazy because those are just indicators. They are essentially indicative rates. They are not executable rates. An executable rate is a rate that somebody is willing at this time to fulfill your transactions for at that time. Meaning you have gotten the rate from your, your OTC desk or from your on and off-ramp partner, and that is the rate that they are willing to do the transaction within a particular time frame. Okay, and so you have that, you have that executable rate, you add your cost to the executable rate. How much does it cost me to have this wallet infrastructure to hold this USDC that I'm doing on that net? How much does it cost me to do that? How much does it cost me to collect the naira? How much will it cost me to pay out the KES? How much does it cost me to have a support team, to have a reconciliation team, to have a compliance team? How much did it cost for the KYC and KYB that needed to happen for this transaction to happen? How much does it cost, right? You add that together plus your margin, and that becomes the rates that you show your consumer, the final rates, right? When you show your customer that final rates you are then able to fulfill- you're then able to- the customer accepts that rate, right, confirms it, and then you are able to move forward. If you don't show your customer the rate enough for it to- if you don't show your customer rates enough for the customer to accept it and the timing that it will take for the transaction to happen, what you are doing is rage baiting your customer. What you are doing if you tell your customer, oh, I'm going to give you instant transfer- now, that's another problem that products make. You have to be able to define what payment experience are you giving your customer. Am I allowing you to be able to transfer, or am I allowing you to be able to do instant transfer? 2 different things. With instant transfer, instant transfer needs 2 things to be true, or one or 2 things to be true. One, pre-funding or a credit line. Because instant transfer means that the minute you make your payments, I, I fulfill it at the other end. I set it at the other end. That's what instant transfer means. There's no time lag in between. Maximum time lag for interest, as far as like 5 minutes, 7 minutes max. If you don't have pre-funding or a credit line that can help for both ends, then you are not offering instant transfer, and it's okay to not offer instant transfer. You can offer transfer and let the customer know at what time am I supposed to receive this. This transaction will take you 30 minutes. We have all used P2P platforms before and you will see the time there. They'll tell you this customer 15 minutes, this one 30, this one 1. If you do not give your customers expectation and you just let them decide the expectation by themselves You are ragebaiting them and they will ragebait you right back, right? So you need to be able to gauge that expectation with your consumer. The best products, the best crypto products that solve for cross-border movements are the ones that make the rails disappear. We are no longer in novelty. The blockchain and stablecoins, we have moved past the point of novelty. We can all no longer deny that we are all financial orchestrators. We're no longer at the fringe of, of the financial system building some new fancy things. No, we are now smack in the middle. We are smack in the middle of conversations. We're smack in the middle of orchestration. So you are not- it's no longer novelty. You need to be able to think like electricity, like I can turn on the lights and the bulb comes on. Nobody cares at the internal what's going on there, what's power up. Nobody wakes up in the morning and says, I want to use HTTPS. Nobody does that. I want to just go on the website and type www. and move on. In fact, I don't even want to type www. I want to type google.com and move on, right? So that is how you need to think about blockchain technology. It should no longer be Except, except again, you are not outside the scope of my conversation. The scope of my conversation is cross-border movements within Africa. Except what you are actually building is a crypto-native product, and crypto is the blockchain technology, and crypto is the entire mood. You want to make sure the customer sees that it is crypto, they get to choose their coin. That's a different conversation, right? But if you are building for cross-border movements, you have to mimic an experience that the customer already knows. So you have to make sure that it disappears in the underneath. I want to be able to see my codes, confirm the codes. I see what is transferred, what settled. I don't need to see this bit of it. As a customer, I don't need to see this stablecoin settled, not necessarily. I just need a simple end-to-end system that makes sure that everything runs the way that it should. Your middle layer is what turns your business into a functional business. We have talked about this, right? All of this pricing policy, routing limits, all of that, it turns your business into that. We've talked about executable FX, and we've talked about how, as a, as a startup and as a scale-up, this is what I recommend that you do. You get your partners, you get your FX, you get your liquidity providers, you get them to come inside, and you make sure that you are pricing in a way that every transaction that you do is successful. You have to start thinking like a banker. You are no longer only building a fringe technology. You are a bank. You are a bank movement. You are part of a settlement layer. And so you have to think like that if you are going to successfully build a product, a payments product, or a payment rail to solve Africa's cross-border economy. Right, so finally I want to talk about things that you have to own, the things you have to partner early on, and the things you must never outsource mentally. Even if you outsource it because you can't do everything by yourself, you must never outsource them mentally. Somebody somewhere, a part of your company, must always remember that regulatory responsibility exists. It exists even if you are partnering with compliance partners, right? You use Flutterwave for your on and off-ramp, right? So Flutterwave helps you do the collection, it helps you convert it into crypto, it helps you deliver it to your customer. And because it is in the CBN sandbox and it has its VASP license, it's able to give you a compliance cover for that interaction. But you must always remember, a regulatory responsibility exists, and one day it can shift to you. And so what do you do when that happens? You must think about your funding policy. How are we solving for that? Are we getting the credit line? If I'm doing instant transfer, am I getting the credit line, or am I pre-funding for every transaction that happens, right? You must think about exceptions and refund ownership. If something goes wrong, who refunds it? And finally, you must think about counterparty and support risk. Okay, these are the things that you must think about. You must always think about these things before you are able to say that you have built a product. I was going to do a little exercise, but unfortunately we don't have time for that. Thank you.

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.