What USDT is, in one paragraph
USDT, or Tether, is a stablecoin: a token issued on public blockchain networks whose value is intended to stay close to one US dollar. USDC is a second stablecoin with the same goal and a different issuer. For a merchant, the practical meaning is that you can be paid in something dollar-denominated that moves at internet speed and settles without a bank in the middle.
The word stable is doing a lot of work and deserves the scepticism. A stablecoin holds its value because its issuer maintains reserves and because the market believes they can be redeemed. That belief has wobbled before and can wobble again. This is a different risk profile from Bitcoin, not an absence of risk.
When it actually makes sense for a Kenyan business
There are four situations where stablecoin acceptance earns its place, and a lot of situations where it does not.
You are paid from outside Kenya. This is the strongest case. A client in Dubai, London or Nairobi-adjacent East Africa can settle an invoice in minutes at a network fee that does not scale with the amount, instead of a wire that takes days and loses money to correspondent banks and conversion spreads.
You sell to the diaspora. Cross-border card payments to Kenyan merchants get declined by fraud rules more often than merchants realise, and the customer usually does not tell you why they gave up. A stablecoin option routes around the card networks entirely.
Your goods are high value or hard to recover. A settled stablecoin transfer cannot be charged back. If you ship electronics, run a travel business or deliver services that cannot be un-delivered, removing reversal risk is worth more than the fee difference.
You already price in dollars. Hosting providers, SaaS businesses, exporters and consultants with USD price lists get a currency match rather than two conversions.
If instead every one of your customers is a Kenyan consumer paying in shillings from an M-Pesa balance, stablecoins add a second option almost none of them will use. Offer M-Pesa properly first.
The network matters more than the token
USDT is not one thing. The same token exists on several independent networks, and a transfer sent on the wrong one does not arrive. This is the single largest source of lost funds in stablecoin payments, and it is a user-interface problem rather than a technology problem.
The networks differ in ways that matter to your buyer. Fees range from negligible to noticeable. Confirmation times range from a couple of seconds to a minute or two. Wallet support varies, and so does which network your particular customer already holds a balance on.
A good checkout removes the guesswork: the buyer picks the network they are sending from, and is then shown an address and an exact amount for that network specifically. Never let a buyer copy an address without seeing which network it belongs to, and never publish a single address in a WhatsApp message and hope.
You do not have to hold crypto to accept it
This is the part most merchants get wrong when they dismiss the idea. Accepting a stablecoin payment does not require you to open a wallet, learn about seed phrases, or carry a token balance on your books.
In a checkout flow with settlement, you set what you want to be paid in. If you choose shillings, the buyer sends USDT and you receive KES over M-Pesa. You never touch a wallet and your accounts stay in one currency. If you choose USDT, you hold a dollar-denominated balance you can withdraw. Both are legitimate; the choice is a treasury decision, not a technical one.
The corollary is that if you do choose to hold USDT, you have taken on a position and the operational responsibility that goes with it. Decide that deliberately rather than by leaving a default setting alone.
The risks nobody puts in the marketing copy
Irreversibility cuts both ways. It protects you from chargebacks and it also means a payment sent to the wrong address, or on the wrong network, is generally gone. Your refund process has to be deliberate, because there is no card network to appeal to.
The quoted amount has a shelf life. A stablecoin amount calculated against a shilling price is only valid for a window. If a buyer opens a checkout page, wanders off and pays two hours later, that is either an expired session or a mismatched amount. Short expiry windows are a feature, and they will occasionally annoy a customer.
Depeg risk is real if you hold. A stablecoin that trades below a dollar for a period is a loss on a balance you are carrying. Settling straight to shillings removes this exposure entirely.
Records and tax are your responsibility. Kenyan tax treatment of digital-asset transactions has moved several times in recent years and continues to evolve. Keep complete records of every payment, the shilling value at the time, and the counterparty, and get that treatment confirmed by an accountant who has looked at current KRA guidance. Nothing in this guide is tax advice.
Customer education is a cost. Some buyers will need help. Budget a support script for the three questions that always come up: which network, why the amount has decimal places, and how long they have to send.
How to start without betting the business on it
Add it as a second option, not a replacement. Keep M-Pesa as the default for local buyers and let the stablecoin method sit alongside it for the customers who want it.
Settle to shillings at first. It gives you the upside, cross-border payments that arrive quickly and cannot be reversed, without taking on a currency position while you are still learning the operational side.
Start with the customers who asked. Almost every merchant who adopts stablecoin acceptance does it because a specific client requested it. Serve that client, watch what breaks, then decide whether to promote it more widely.
Test the failure paths before the happy path goes live. Send yourself a payment on the wrong network, let a session expire, and issue a refund. Knowing what those look like is what separates a merchant who can support this from one who cannot.