Every account is reviewed before it can move money
Pycue puts collections, payouts, messaging, airtime and data bundles behind a single API — with per-organization isolation, explicit approval for every capability, and settlement that happens exactly once.
curl https://api.pycue.com/api/v1/deposits \
-H "Authorization: Bearer $PYCUE_KEY" \
-H "Content-Type: application/json" \
-d '{
"externalUserId": "user_4417",
"amount": "250.00",
"phoneNumber": "0241234567",
"network": "MTN",
"clientReference": "order-8891"
}'201 Created
{
"transaction": {
"id": "0f3c…",
"status": "PENDING",
"amount": "250.00",
"currency": "GHS"
}
}The balance is credited only after the network confirms, and only after Pycue re-verifies that confirmation.
Transaction lifecycle
Capabilities
Pycue stays deliberately narrow. It runs mobile money, messaging and airtime on behalf of organizations that already own their customer relationships.
Prompt a payer for any amount and receive a callback when the network confirms. Your customer is charged the exact amount you requested — nothing is added to their side of the transaction.
Send money to a recipient's mobile-money wallet, or raise a cashout request from your workspace for a Pycue administrator to review and pay out directly.
Prepaid messaging credits are drawn down one unit per recipient. Build verification flows on top of the same keys you use for payments.
Purchase airtime for a recipient or sell data bundles. Package catalogues are read live from the provider so you are never pricing against stale data.
How money moves
A charge applied by Pycue is a matter between Pycue and your organization — it is never added to what your customer pays. Your integration keeps recording the gross it collected.
Collections
payer charged 250.00 · organization credited 237.50 · Pycue 12.50
Payouts
balance − 250.00 · recipient receives 237.50 · Pycue 12.50
Rates are agreed per organization and can be zero. See how charging works.
Networks
Requests carry the network explicitly, so you always know which operator a payout is routed through. Amounts are accepted and returned as decimal strings and stored internally as integer pesewas.
Operating principles
Money movement is unforgiving of shortcuts. These are the four decisions Pycue is built around.
Self-registration does not grant access. A new organization is held at PENDING_APPROVAL until a Pycue administrator reviews it, and collection and payout access are approved separately on request.
The calling organization is derived from the API key, never from a request field. Every query, balance and transaction is scoped by that identifier, so the same customer ID in two organizations is two unrelated customers.
Funds move only through a conditional database transition paired with immutable ledger rows in the same transaction. A replayed webhook, a retried request or a concurrent caller cannot double-credit.
Pycue never acts on a callback alone. Each one is treated as a claim, re-verified with an authoritative server-to-server check, and only then applied.
Register with your organization details and verify the phone number you control. Access is granted once a Pycue administrator has reviewed the account.