Welcome to eTulip
A clear starting point for integrating Mobile Money collections.
One collection API, operators enabled on your account and a shared transaction status flow. This guide describes available features and access requirements.
Before you start
Your merchant account must pass KYC, be enabled for live use and have permission for the required country and operator.
ETULIP / API
IllustrationOne route for every enabled operator
The route stays the same. Your request specifies an operator enabled on your account.
Your application
POST /v1/collections
Enabled operatorBased on your account
202 · pendingRequest recorded
Webhook or status check
succeeded / failed
Same endpoint
POST /v1/collections{ "operator": "moov_tg", "amount_minor": 1000, "currency": "XOF" }Choose a guide
Authentication
Server credentials, keys and permissions.
Collections
Create a request and follow its result.
Balances and fees
Understand operator balances and movements.
Webhooks
Receive signed status updates.
Iframe checkout
Embed a payment interface on your site.
Your first collection
Get access
Complete KYC and obtain country and operator permissions. Keep your private API key on your server.
Create the request
Call POST /v1/collections with an idempotency key unique to the intended request.
Confirm the result
Wait for the signed webhook or check status. A 202 response only means the request was accepted for processing.
Transfers
Payouts are not public yet. The Qosic contract must be integrated before real money is sent.