- Banks Don't Have to Choose Between Building and Opting Out
- The Bank Owns the Customer; the Provider Runs the Machine
- One Model Powers Inflows, Liquidity, and Collections
- Integration Sits on Top of Core Banking, Not Inside It
- Control Doesn't Require Operating the Machine
- Pilot One Use Case Before You Scale
- Final Thoughts
Ask most bank executives about offering crypto-enabled services, and you hit the same wall: “We’d have to build a whole crypto division, hire engineers we don’t have, and own risks we don’t understand.” So the project dies in committee, and customers who want these services quietly take them elsewhere. The belief underneath that decision is that offering a crypto product means building and running the crypto technology.
It doesn’t, and your own card business proves it. No bank in Nigeria or Ghana built the Mastercard or Visa network. You don’t run the global switching infrastructure, you didn’t invent the chip on the card, and you certainly don’t maintain the rails that authorize a payment in seconds. You own the customer, the account, and the brand on the card. You consume the rest as infrastructure. Crypto-enabled services work the same way, and this article walks through that operating model: who owns what, what it powers, how it plugs in, and how to start small.
Banks Don’t Have to Choose Between Building and Opting Out
The build-or-opt-out framing is a false choice. There is a third option that banks use every day for almost every modern service: consume the capability as infrastructure.
You already do this everywhere. You don’t run your own SWIFT network, host your own card-processing switch from scratch, or build your own SMS gateway. You rent specialized infrastructure and put your brand and your customer relationship on top. Crypto is not a special exception that demands you suddenly become a blockchain engineering shop. It is one more capability you can stand on top of, the same way you stood on top of the card networks decades ago.
The Bank Owns the Customer; the Provider Runs the Machine
The clean way to think about this is a division of labor, like a restaurant that owns the dining room, the menu, and the relationship with every guest, while a supplier delivers prepped ingredients through the back door. The guest never sees the supplier. The experience is entirely the restaurant’s.
The bank owns the things that are its actual moat: the customer relationship, the brand, the distribution, the deposit accounts, and the regulatory accountability that comes with being a trusted institution.Â
The provider owns the machine in the back: wallet generation, private key management, on-chain monitoring, automatic conversion, AML screening, webhook notifications, and uptime. Breet’s Crypto Payment API is built to be that back-of-house layer, so your customers experience a crypto-enabled service under your brand while the parts that require a blockchain operations team sit with people who do only that.
One Model Powers Inflows, Liquidity, and Collections
The same infrastructure layer powers several products, which is what makes it worth integrating once. Three are immediately useful to a bank.
- Crypto-funded inflows. A customer or their counterparty pays in crypto, and it settles to the customer’s naira or cedis account automatically. The customer gets paid; you keep the relationship and the deposit.
- Stablecoin liquidity. Treasury and merchant clients who deal across borders can hold and move stablecoin value and convert to fiat on demand, giving your business customers a tool your competitors may not offer yet.
- Invoicing and collections. Business banking customers can issue crypto invoices and receive the fiat equivalent, so their accounts receivable process works the way it always has, just with a wider set of payers.
One integration, several products, your relationship managers can actually sell.
Integration Sits on Top of Core Banking, Not Inside It
The fear that this means open-heart surgery on your core banking system is the wrong picture. The right picture is an extension, not a transplant.
The model is an API and a dashboard that sit on top of your existing systems, not code rewritten inside your core. Your core banking platform keeps doing what it does. The crypto capability connects through defined interfaces, the same way a new card product or a new payment channel connects. Because the heavy machinery already exists and is being consumed rather than built, the timeline is measured in days, not the multi-quarter project a from-scratch build would demand.
Control Doesn’t Require Operating the Machine
The instinct that control requires ownership is understandable, and wrong in this case. You can hold the controls without running the engine, the way a pilot commands an aircraft without having built the turbines.
Compliance accountability stays with you, and the infrastructure is built to support that rather than undermine it. KYC and AML screening run in line with every transaction.Â
The infrastructure operates within recognized frameworks, including PCI DSS and the Nigerian Data Protection Act. Audit trails and reporting give your compliance and risk teams the visibility they need to respond to regulators. You get governance and oversight without taking on the operational burden of running wallets and monitoring chains yourself.
Pilot One Use Case Before You Scale
You don’t have to bet the bank to learn whether this works. The smart move is to pilot narrow, the way you would test a new branch format in one city before rolling it nationwide.
Pick a single use case with a clear owner, say crypto-funded inflows for a defined segment of business customers. Set success metrics up front: adoption, transaction volume, support load, customer feedback.Â
Run it, measure it, and use the results to decide whether and how to widen. Because the integration is light and the infrastructure scales on demand, expanding from a pilot to a full product is a commercial decision, not another engineering project.
Final Thoughts
Banks have been consuming infrastructure they didn’t build for as long as card networks have existed. Crypto-enabled services are not a reason to abandon that model; they are a reason to apply it again. Own the customer, rent the machine, keep the control.
The banks that move first will offer services that their competitors are still arguing about in committee. Book a walkthrough, and we will show you what the back-of-house layer looks like under your brand.
