Which African countries does pawaPay support?

pawaPay supports mobile money operations across multiple African corridors including Uganda (UGX), Kenya (KES), Tanzania (TZS), Ghana (GHS), Cameroon (XAF), and others. Each corridor corresponds to specific mobile money operators in that country. Available corridors can change - check the API documentation for the current list.

How do bulk payouts work?

POST /v2/payouts/bulk accepts an array of payout objects, each with a unique payoutId, recipient MSISDN, amount, and corridor. Each payout processes independently - a failure in one does not affect others. Individual payout status is tracked via GET /v2/payouts/{payoutId} and callbacks are sent per payout.

Can I issue refunds for collected deposits?

Yes. POST /v2/refunds creates a refund against a completed deposit transaction. You provide the original depositId and a unique refundId. Refund status is tracked via GET /v2/refunds/{refundId} and callback notifications are sent when the refund settles.

How do I collect a mobile money payment through Jentic?

Search Jentic for 'collect a mobile money deposit', load the operation schema for POST /v2/deposits, and execute with the customer MSISDN, amount, currency, and corridor. Jentic injects the Bearer token and returns the deposit status. Install with pip install jentic.

What is the difference between payouts and remittances?

Payouts disburse funds within a single country corridor (same currency). Remittances transfer funds across borders between different countries and currencies, with pawaPay handling the conversion. Both support individual and bulk operations with the same callback notification mechanism.

Can I limit what my agent is allowed to do with the pawaPay API?

Yes. Because you run Jentic One yourself, you decide exactly which pawaPay operations your agent may call, so you can allow read-only actions like checking a deposit status with GET /v2/deposits/{depositId} or reading wallet balances with GET /v2/wallet-balances while leaving money-moving operations out of scope. Since pawaPay carries the deposit, payout, and remittance targets in the request body, initiating payouts via POST /v2/payouts or issuing refunds via POST /v2/refunds is not available to the agent unless you explicitly add those operations. Your pawaPay Bearer token stays with your own Jentic One instance and is injected at execution time, so it never enters the agent's prompt or logs.