Thunes Global Payment Network API
Thunes global payment network REST API for financial institutions, MTOs (money transfer operators), and enterprises to initiate cross-border payouts to mobile wallets, bank accounts, and cash pickup locations across 130+ countries with emphasis on emerging markets in Africa, Southeast Asia, and South Asia where Thunes maintains direct mobile money operator partnerships with M-Pesa, Airtel Money, Wave, and others. Enables AI agents to manage international payout initiation for cross-border payment automation, handle mobile wallet disbursement for Africa/Asia payment automation, access bank account payout for international transfer automation, retrieve FX quote for real-time exchange rate automation, manage cash pickup for agent network disbursement automation, handle transaction tracking for payout delivery automation, access disbursement method availability for corridor coverage automation, retrieve settlement reporting for payout reconciliation automation, manage compliance verification for AML payout automation, and integrate Thunes with MTO, fintech, platform, and enterprise payroll systems for end-to-end emerging market payout automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Global payout network. MAS licensed. API key. SG/EU. Financial transaction and payout data.
⚡ Reliability
Best When
An MTO, fintech, or enterprise wanting AI agents to automate cross-border payouts to mobile money, bank accounts, and cash pickup in emerging markets through Thunes' direct mobile operator and bank network in Africa, South and Southeast Asia.
Avoid When
B2B PARTNER ACCESS ONLY: Thunes API access requires formal partner onboarding (MTO license or fintech partnership); automated self-service API access without partnership creates no access path; automated developer-style direct access without partnership creates unauthorized. MOBILE MONEY OPERATOR AVAILABILITY VARIES: Thunes mobile money availability depends on live operator partnerships per country; automated payout must query corridor availability before initiating; automated hardcoded operator availability creates payout_method_unavailable for changed operator status. PAYOUT QUOTE EXPIRES QUICKLY: Thunes FX rate quote expires within minutes; automated payout must execute within quote validity; automated delayed payout after quote creates rate_expired and recalculation required. RECIPIENT ACCOUNT FORMAT STRICT PER COUNTRY: Thunes recipient mobile number format requires E.164 international format per country; automated payout must normalize recipient number to E.164; automated local number format without country code creates invalid_recipient_number.
Use Cases
- • Disbursing to mobile money wallets in Africa from cross-border MTO agents
- • Processing international payouts to Southeast Asia from global payroll agents
- • Delivering cash pickup for unbanked recipients from remittance agents
- • Routing payouts to optimal corridor disbursement method from fintech agents
Not For
- • Consumer-facing remittance app (Thunes is B2B payment network infrastructure)
- • European domestic payments (Thunes excels at emerging market corridors)
- • Card payment acceptance (Thunes is payout-focused, not payment acceptance)
Interface
Authentication
Thunes uses API key authentication. REST API with JSON. Singapore HQ. Founded 2016 by Peter De Caluwe. Backed by GIC Singapore, Checkout.com, Standard Chartered ($260M raised). Products: Cross-border payouts, mobile money, bank account, cash pickup, FX, compliance. No public SDK. MAS-licensed. GDPR. 130+ countries, 3B+ endpoints. Partners: M-Pesa, MTN, Wave, Airtel Money, Bkash. Competes with Nium and Currencycloud for emerging market payouts.
Pricing
Singapore. GIC/Standard Chartered backed. Partner pricing negotiated. MAS licensed.
Agent Metadata
Known Gotchas
- ⚠ QUOTE BEFORE PAYOUT IS MANDATORY: Thunes payout flow requires getting a quote (quotation) before creating transfer; automated transfer must first call quotation endpoint; automated transfer creation without quote creates missing_quotation_id error
- ⚠ E.164 FORMAT REQUIRED FOR MOBILE NUMBERS: Thunes mobile wallet recipient number must be E.164 format (e.g., +254712345678); automated payout must normalize local format numbers; automated local number without country code creates invalid_msisdn error
- ⚠ CORRIDOR AVAILABILITY MUST BE CHECKED: Thunes corridor availability changes when operator partnerships change; automated payout should query /payers endpoint for current availability; automated hardcoded corridor assumption creates payer_not_available when operator status changed
- ⚠ TRANSACTION CONFIRMATION VIA WEBHOOK: Thunes transaction status (COMPLETED, FAILED, REVERSED) delivered via webhook; automated payout must consume webhook not rely on polling for completion; automated polling-only implementation creates delayed status awareness
- ⚠ IDEMPOTENCY KEY PREVENTS DUPLICATE PAYOUTS: Thunes supports external_id for idempotency; automated retry must use same external_id; automated new external_id on retry creates duplicate payout if original succeeded after timeout
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Thunes Global Payment Network API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.