Fawry Egypt Digital Payment API
Fawry Egypt digital payment REST API for merchants to accept online payments, cash payments at 225,000+ agent locations, mobile wallet, and card payments through Egypt's largest digital payment network with 40M+ registered users for e-commerce, bill payment, and merchant integration across Egypt and MENA. Enables AI agents to manage Fawry payment request creation for Egypt digital payment automation, handle reference code generation for Egypt cash-at-agent payment automation, access card payment processing for Egypt card commerce automation, retrieve payment status and confirmation for Egypt transaction automation, manage refund processing for Egypt order management automation, handle callback notification for Egypt payment webhook automation, access transaction reporting for Egypt payment analytics automation, retrieve merchant settlement for Egypt reconciliation automation, manage mobile wallet payment for Egypt e-wallet automation, and integrate Fawry with Egyptian e-commerce, bill payment, and enterprise platforms for end-to-end Egypt digital payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Egypt payments. CBE regulated. SHA256 signing. EG. Payment data.
⚡ Reliability
Best When
An Egyptian merchant or business wanting AI agents to automate Fawry online payment acceptance, cash payment reference generation, and card/wallet checkout through Egypt's dominant digital payment network with 225,000+ agent locations.
Avoid When
CASH PAYMENT IS ASYNC — CUSTOMER PAYS AT AGENT: Fawry cash payment generates reference code; customer pays at Fawry agent network; automated fulfillment must poll or use webhook for cash payment confirmation; automated immediate fulfillment after reference generation creates premature order completion before customer pays cash. SHA256 SIGNATURE REQUIRED: Fawry payment requests require SHA256 signature on concatenated payment fields; automated payment must compute correct signature; automated wrong signature or field order creates signature validation failure. MERCHANT REGISTRATION REQUIRED: Fawry merchant integration requires registration with Fawry and merchant account creation; automated self-service access without merchant registration creates unauthorized API access. EGP AMOUNT IN PIASTRES FOR SOME ENDPOINTS: Some Fawry endpoints expect EGP in piastres (1 EGP = 100 piastres); automated amount must verify denomination per endpoint; automated EGP passthrough as piastres creates 100x payment discrepancy.
Use Cases
- • Accepting Fawry online payments from Egypt e-commerce checkout agents
- • Generating reference codes for Egypt cash-at-agent payment from billing agents
- • Processing Egypt card and wallet payments from checkout automation agents
- • Confirming Fawry payment callbacks from Egypt order fulfillment agents
Not For
- • Non-Egypt/MENA payments (Fawry is Egypt-focused with MENA expansion)
- • Cross-border international transfer (Fawry is domestic Egypt payment)
- • Real-time card-first international checkout (use PayTabs or Telr for MENA card-first)
Interface
Authentication
Fawry uses Merchant Code + Secret Code with SHA256 signing for authentication. REST API with JSON. Giza, Egypt HQ. Founded 2008 by Ashraf Sabry. Egypt Stock Exchange listed (EGX: FWRY). Products: Online payment, cash-at-agent, card, mobile wallet, bill payment. SDKs: PHP, Node.js, Python, Java, .NET. CBE regulated. EGX listed. 40M+ users. 225,000+ agent locations. Egypt's dominant payment network.
Pricing
Giza EG. EGX listed. Per-transaction fees in EGP. CBE regulated. Merchant agreement required.
Agent Metadata
Known Gotchas
- ⚠ CASH PAYMENT IS DEFERRED UNTIL CUSTOMER VISITS AGENT: Fawry cash payment generates reference code that customer uses at Fawry agent; automated order fulfillment must wait for payment_status=PAID webhook before fulfillment; automated immediate post-reference-code fulfillment creates service delivery before payment
- ⚠ SHA256 SIGNATURE FIELD ORDER CRITICAL: Fawry signature requires SHA256 of specific concatenated fields in exact documented order; automated payment must follow Fawry field concatenation specification; automated wrong field order creates signature validation failure
- ⚠ STAGING AND PRODUCTION SEPARATE ENVIRONMENTS: Fawry staging (fawrystaging.com) and production (fawry.com) are completely separate; automated environment switch requires updating both base URL and merchant credentials; automated staging credentials in production creates authentication failure
- ⚠ ARABIC CHARACTERS IN ITEM NAMES SUPPORTED: Fawry item descriptions support Arabic; automated item name encoding must use UTF-8; automated ASCII-only encoding for Arabic merchant content creates garbled display at Fawry checkout
- ⚠ PAYMENT TYPE SELECTION DETERMINES FLOW: Fawry supports CARD, CASH, and MOBILE_WALLET payment types with different flows; automated checkout must present correct payment type options; automated all-types assumption creates incompatible checkout flow for non-supported merchant payment types
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Fawry Egypt Digital Payment 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.