Crypto in. Local money out.
Fund an approved transfer with USDT or USDC and pay a recipient in an available local currency, including planned KES routes.
See delivery scopeCrypto from one side. Local currency on the other. We’re building payment journeys around the way people earn, send and receive.
Illustrative UK → Kenya route. Market and provider approvals pending.
Explore the four payment patterns we’re designing. Change the funding type or reverse the direction to see how a planned journey fits together.
Supported digital wallet
Approved local bank or mobile-money route
Illustrative route, not an available quote. UK ↔ Kenya requires approval in each direction. Rates, fees, limits and delivery methods will be shown for enabled routes.
These examples describe the product direction. UK ↔ Kenya is not an activated corridor. Other markets will appear only after their collection, conversion and payout routes are approved.
Explore the shared payment capabilities and the later personal account launch. Each feature links to its delivery scope.
Fund an approved transfer with USDT or USDC and pay a recipient in an available local currency, including planned KES routes.
See delivery scopeFund through an approved fiat collection route and deliver USDT or USDC to a verified recipient wallet on an enabled network.
See delivery scopeReview fees, exchange rate, recipient amount and quote expiry before approving a supported transfer or conversion.
See delivery scopeTrack payment progress and exceptions, then review transaction records and statements across funding, conversion and payout.
See delivery scopeAccept an identified customer payment for a business, match it to the correct invoice or reference, and manage unmatched funds.
See delivery scopeA dedicated consumer sending experience after its onboarding, market permissions, limits and support model are approved.
See delivery scopeSelect an enabled funding method and the recipient’s preferred destination. Eligibility and identity checks come first.
See the asset or currency, network, fees, amount due and expected payout before you approve.
Track funding, conversion and payout. If a provider outcome is uncertain, the transfer is reviewed before any retry.
The initial release focuses on approved businesses and API partners, including payments to individual recipients and identified customer payments to businesses.
Open personal sender accounts are a later release, with their own market permissions, verification, limits and support. The Personal page lets you follow that product as it takes shape.
Follow personal sendingThat is a planned route pattern: receive an approved USDT or USDC transfer, screen and confirm it, execute the quote and pay KES through a contracted Kenyan rail. UK sender eligibility and the Kenyan payout method must both be approved before activation.
Yes, the architecture includes the reverse pattern. An approved fiat collection can fund a conversion and a payout to a verified wallet on an enabled network. Availability is specific to the country, provider, asset and network.
No. KES, EUR, USD, GBP, USDT and USDC are the initial product scope. Each direction and payment method needs its own enabled route; the currency list does not promise worldwide availability.
Personal account opening and live payments are not available yet. The feature map separates the core payment rails from the later consumer sender launch.