Build on
Itunda.
One place to understand the integration surfaces that exist today — payments, embedded apps and the merchant ecosystem.
Pick the surface.
Follow the path.
Each product has a focused path so developers can move from understanding to implementation without guessing which system they need.
Pay Itunda
External checkout through the payment API, hosted checkout, idempotency and webhook delivery.
02 · EMBEDDED APPSSaronite
Partner registration, mini-app submission, human review and approved catalog distribution.
03 · MERCHANTSMerchant ecosystem
Merchant registration, QR payment collection, settlement and business tooling.
A small contract
to start with.
The current Pay Itunda integration exposes a payment-creation endpoint and returns a hosted checkout destination. Credentials stay server-side.
POST /api/v1/pay/payments
X-Api-Key: sk_test_...
Idempotency-Key: <unique-request-key>
{
"amount": 1000,
"currency": "RWF",
"reference": "order_123"
}
→ payment key + hosted checkout URLConnect once.
Build around real systems.
The Business surface sits beside the consumer product. That separation keeps customer experiences simple while giving partners room for APIs, review workflows and merchant operations.
Credentials
Use API credentials on the server. Never expose secret keys in client-side code.
Events
Payment status and cancellation events provide a server-side path for keeping your system in sync.
Review
Mini-app submissions follow registration and human review before approved experiences enter the catalog.
Ready to build?
Start with a payment integration or submit an experience for Apps in Itunda.