FOR BUILDERS / PAYMENTS WITH CONTEXT
Your product.
A clearer payment rail.
Build a Kenyan shilling-to-Bitcoin journey for your users. Start in the sandbox, then request access for an approved buy integration.
BUY ONLY AT LAUNCHM-Pesa in.
M-Pesa in.
Lightning sats out.
Build the quote, collection and delivery experience around a clear payment status. Production access is reviewed separately from sandbox access.
- Sandbox: simulated payments for integration work.
- Production: approved partners and buy-only scope.
- Sell and merchant KES payouts: not available in production.
ENVIRONMENTS / CHECK THE LABEL
# Sandbox · simulated money https://sandbox.vukia.app/v1 vk_test_… # Production · approved buy access https://api.vukia.app/v1 vk_live_… # Keep API keys on your server. # A test result is not a live receipt.
THE NEXT STEP
Built the sandbox flow?
Let’s review the real one.
Request production access.
Use the access instructions in the docs. Include enough context to review your integration and its payment responsibilities.
- Your product, website and intended use.
- Countries, payment direction and expected volumes.
- Sandbox integration results and callback behaviour.
- Your support contact and approach to unresolved payments.
Never email API secrets, wallet seeds, PINs or customer identity documents. Access is subject to review; an email is not an approval.
Less guessing. More building.
The API docs have the request and response details.