pawaPay Merchant API V2
✓ Official Vendor SpecPaymentsPayouts Transfersbearer24 EndpointsREST
For Agents
Process mobile money deposits, payouts, and remittances across African markets. Handle bulk disbursements, refunds, wallet balance checks, and payment page creation for mobile money transactions.
Use for: I need to collect a mobile money payment from a customer, I want to send a payout to a mobile money wallet, Process a bulk payout to multiple recipients, Check my wallet balance for a specific corridor
Not supported: Does not handle card payments, bank transfers, or non-African markets — use for mobile money deposits, payouts, and remittances in African corridors only.
The pawaPay Merchant API V2 enables businesses to send and receive mobile money payments across African markets. It provides 24 endpoints covering deposits (collections from customers), payouts (disbursements to recipients), remittances (cross-border transfers), refunds, payment page creation, wallet balance queries, and financial statements. The API supports both individual and bulk payment operations with callback notifications for asynchronous payment status updates.
Install Jentic One Beta
Connect the pawaPay Merchant API V2 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the pawaPay Merchant API V2, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with pawaPay Merchant API V2 API.
Collect mobile money deposits from customers across multiple African corridors
Disburse payouts to mobile money wallets individually or in bulk batches
Process cross-border remittance transfers between supported African countries
Issue refunds against completed deposit transactions
Generate hosted payment pages for customer-initiated mobile money collections
Query real-time wallet balances across active mobile money corridors
Retrieve financial statements with transaction-level detail for reconciliation
Use Cases
Patterns agents use pawaPay Merchant API V2 API for, with concrete tasks.
★ Mobile Money Collection
Collect payments from customers via mobile money wallets across African markets using the deposits endpoint. Each deposit request specifies the amount, currency, recipient MSISDN (mobile number), and corridor. The API processes the request asynchronously and delivers status updates via configured callback URLs, supporting high-volume collection scenarios.
Create a deposit of 5000 UGX from mobile number '+256700123456' via POST /v2/deposits with a unique depositId and verify the callback confirms success
Bulk Payout Disbursement
Disburse funds to multiple mobile money recipients in a single API call using the bulk payouts endpoint. This supports payroll, marketplace seller payments, and mass disbursement scenarios. Each payout in the batch is processed independently with individual status tracking, and failed payouts can be retried without reprocessing the entire batch.
Submit a bulk payout of 3 recipients via POST /v2/payouts/bulk with amounts in KES and verify each payout status via GET /v2/payouts/{payoutId}
Cross-Border Remittance
Process international mobile money transfers between supported African corridors. The remittances endpoint handles currency conversion and routing between countries, supporting both individual and bulk transfer operations. Each remittance is tracked independently with callback notifications for settlement confirmation.
Initiate a remittance transfer from Kenya (KES) to Uganda (UGX) via POST /v2/remittances with source and destination mobile numbers
AI Agent Mobile Payment Orchestration
AI agents process mobile money transactions across African markets through Jentic without managing Bearer token lifecycle or callback webhook infrastructure directly. Agents search for payment operations like 'collect a mobile money deposit' and receive structured schemas with authentication handled by the Jentic vault.
Search Jentic for 'collect a mobile money payment', load the operation schema for POST /v2/deposits, and execute with the customer MSISDN, amount, and corridor parameters
Key Endpoints
24 endpoints — the pawapay merchant api v2 enables businesses to send and receive mobile money payments across african markets.
METHOD
PATH
DESCRIPTION
POST
/v2/deposits
Create a mobile money deposit (collection)
GET
/v2/deposits/{depositId}
Check deposit status
POST
/v2/payouts
Send a payout to a mobile wallet
POST
/v2/payouts/bulk
Send bulk payouts
POST
/v2/remittances
Initiate a cross-border remittance
POST
/v2/refunds
Issue a refund for a deposit
GET
/v2/wallet-balances
Query wallet balances
POST
/v2/paymentpage
Create a hosted payment page
POST
/v2/deposits
Create a mobile money deposit (collection)
GET
/v2/deposits/{depositId}
Check deposit status
POST
/v2/payouts
Send a payout to a mobile wallet
POST
/v2/payouts/bulk
Send bulk payouts
POST
/v2/remittances
Initiate a cross-border remittance
POST
/v2/refunds
Issue a refund for a deposit
GET
/v2/wallet-balances
Query wallet balances
POST
/v2/paymentpage
Create a hosted payment page
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
pawaPay Bearer tokens for sandbox and production are stored encrypted in the Jentic vault. Agents receive automatic token injection per environment — raw API keys never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'send a mobile money payout in Kenya') and Jentic returns matching pawaPay operations with parameter schemas including required corridor codes and MSISDN formats.
Time to first call
Direct pawaPay integration: 2-4 days for auth setup, corridor configuration, and callback handling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Global payment processing for cards, wallets, and bank debits
Use Stripe for global card and digital wallet payments. Use pawaPay specifically for African mobile money corridors where Stripe has limited coverage.
FAQs
Specific to using pawaPay Merchant API V2 API through Jentic.
What authentication does the pawaPay API use?
The pawaPay API uses Bearer token authentication. All requests require an Authorization header with a Bearer token issued from the pawaPay dashboard. Sandbox and production environments use separate tokens. Through Jentic, Bearer tokens are stored encrypted in the credential vault and injected automatically.
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.
GET STARTED