Fawry
Fawry is Cairo-based Egypt's leading provider of e-payments and digital finance solutions, operating a nationwide network for card, e-wallet, and cash-based bill, merchant, government, and education payments. The FawryPay acceptance platform exposes a server-to-server REST API plus native Android, iOS, Flutter, and React Native SDKs and certified plugins for Magento, Shopify, and WooCommerce that let merchants charge cards (including 3DS), e-wallets, ValU, and bank installments, generate FawryPay reference numbers payable across more than 250,000 Fawry POS locations and partner channels, issue refunds, cancel unpaid orders, and reconcile via signed server notifications. Fawry also offers consumer products (myfawry super app, yellowcard prepaid card, FawryPlus, TicketsMall), enterprise and SME acceptance, pay-out, micro-finance, and consumer-finance services. Fawry is publicly listed on the Egyptian Exchange as FWRY.CA.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Fawry the way a machine reads it — 18 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Fawry scores 29.6/100 (emerging), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Fawry
Each block below is one kind of artifact we hold for Fawry. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Fawry Installments API
Bank installment plans available for a merchant.
Fawry Orders API
Inspect or cancel FawryPay orders.
Fawry Payments API
Create payment requests and charge cards or wallets.
Fawry Refunds API
Refund settled FawryPay orders.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
FawryPay Server API
OPEN COLLECTIONFeatures 11
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 11 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Fawry — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 16
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 16 ·
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Company 4
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fawry · machine-readable index on apis.io