Your rate
Price it yourself.
You independently set your merchant rate. Sargo does not set your rate or take a rate spread.
For merchants
The merchant side
of an order.
Merchants must be verified and hold a supported settlement stablecoin, post their own rates and settle KES from an account in their own name.
- Your rate. You set it.
- Your float. You control it.
- Your rails. You choose what you support.
01 / The loop
Four moves.
Every order.
- 01
Quote.
Set your own rate and choose the order sizes, assets and payment rails you can support.
- 02
Accept.
A consumer selects your offer. Accept only an order you can perform.
- 03
Settle.
Follow the order instructions to send or receive KES. Your merchant side uses a supported proving bank account so the payment can be evidenced if needed.
- 04
Complete.
When the order conditions are satisfied, the funded stablecoin is released or returned according to the escrow rules.
02 / Your control
Your rate.
Your float.
Your rails.
Your float
Two stablecoins. Two networks.
Hold USDT or USDC on Celo or Base. Consumers can start with another supported token or chain; it may be converted into the settlement asset, where a route is enabled for the order.
Your rails
An account in your name.
Use an account in your own name with KCB, Equity Bank or Cooperative Bank. If a payment is disputed, provide evidence from that account. Proof availability depends on the bank’s verifier; otherwise, manual review is required.
Merchants independently set their posted rates. Their commercial margin depends on the rate, costs and completed orders. Sargo does not promise order flow or merchant earnings.
03 / Protection
From funding.
To proof.
01 / Check
Know your side.
Check the amount, rate and payment instructions. Make sure you know who sends KES and who sends stablecoin.
02 / Lock
Stablecoin first.
USDT or USDC locks in escrow on Celo or Base before KES moves. A consumer’s supported source token is converted first, if needed.
03 / Pay
Send. Or confirm.
Sending KES? Pay the account shown. Receiving KES? Check your account before confirming it has arrived.
If there’s a dispute
Payment evidence.
Not just a screenshot.
You create a cryptographic payment proof from your supported bank session using Sargo Verifier.
It is tied to the order and submitted for review. Escrow then follows the order’s configured rules.
The verification service may process authenticated bank-session data, and some proof fields may be recorded on a public blockchain. Check that your bank and your set-up are supported before relying on a proof. See the Privacy Policy and how payment proofs work.
- The consumer sees evidence, not your statement.
- The consumer receives payment evidence — not your bank statement, password, PIN or one-time code.
- Proposed clocks, each with its own start.
- 30 minutes (M-Pesa) or 60 minutes (bank) to pay and mark paid, from when the stablecoin is locked and the order is ready for payment; 3 hours to confirm, from when payment is marked as made; 12 hours for your payment proof, from when the order enters the proof stage and you are notified. Separate proposed clocks, not a total completion time; variations approved by the regulator may apply. Merchants quote honestly, accept only orders they can perform, meet deadlines, keep records and provide evidence where required (Terms, section 9). What follows a missed clock or a disputed payment is set out in the Terms, section 7 and section 8.
- Fees.
- Your rate and all fees are shown before the consumer authorises. Under the proposed model the consumer pays Sargo’s disclosed processing fee from the stablecoin amount on successful settlement; there is no charge on the KES leg and no rate spread.
- What it can show.
- A matching payment sent or received in the records checked. No match means further review, not proof that payment never happened.
04 / Prepare
Bring the
basics.
- 01
Your identity.
Complete identity verification as part of merchant onboarding.
- 02
Your funded wallet.
Hold USDT or USDC on Celo or Base for settlement. The consumer’s starting token and chain can be different.
- 03
Your bank account.
Use an account in your own name with KCB, Equity Bank or Cooperative Bank. If a payment is disputed, provide evidence from that account. Proof availability depends on the bank’s verifier; otherwise, manual review is required.
Merchant interest enquiry
Register merchant
interest.
Tell us about your experience, typical order range, stablecoins and payment rails. This is an enquiry before any activation, not an application for an active merchant account.
An enquiry does not create an account, activate merchant status or authorise an order.
What is stored. Your name, email address, merchant experience, order range, banks, stablecoins and networks, how you heard about Sargo, the time of the enquiry and the version of the Terms and Privacy Policy you agreed to. To limit abuse, a keyed one-way hash of your network address and of your email address is kept for up to an hour and then deleted at the next request. Nothing is emailed when you submit; the page shows a reference instead. See the Privacy Policy.
Preview: test submissions only
This preview stores what you send in an isolated test database so the form can be checked end to end. Test entries are not reviewed by Sargo and do not register real interest. Use example details, not real personal information.
Test enquiry saved.
It was stored in the preview’s test database. It does not register real interest. An enquiry does not create an account, activate merchant status or authorise an order.
This form sends no email. Keep the reference if you contact support@sargo.io.