Paymob
Paymob is a Cairo-headquartered, licensed payment infrastructure provider for the MENAP region. Serving roughly 390,000 merchants across Egypt, Saudi Arabia, the United Arab Emirates, Oman, and Pakistan (with Qatar announced), Paymob unifies card acquiring, regional mobile wallets (Vodafone Cash, Etisalat Cash, Orange Money, STC Pay, Oman Net, EasyPaisa, JazzCash), BNPL rails (Tabby, Tamara, valU, Souhoola, Forsa, Aman), Apple Pay, Google Pay, POS terminals, subscriptions, installments, marketplace payouts, mass disbursement (Paymob Send), and an end-to-end cashless commerce platform (Paymob Sync) behind a single Accept / Intentions API surface.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Paymob the way a machine reads it — 81 machine-readable artifacts across 18 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 — Paymob scores 64.5/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). 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 Paymob
Each block below is one kind of artifact we hold for Paymob. 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 18
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.
Paymob Intentions API
The v1 Intentions API is Paymob's modern entry point for payment acceptance. The merchant backend creates an intention with the secret key and an array of payment_methods (integ...
Paymob Subscriptions API
The Subscriptions Module manages subscription plans (create, list, update, suspend, resume) and per-customer subscriptions billed against tokenised cards. Lifecycle operations c...
Paymob Card Tokens API
Tokenisation surface for the Paymob "Pay with saved card" flow. Lists and deletes tokenised cards and runs both customer-initiated (CIT) and merchant-initiated (MIT) transaction...
Paymob Accounts API
The Accounts API from Paymob — 1 operation(s) for accounts.
Paymob Authentication API
The Authentication API from Paymob — 3 operation(s) for authentication.
Paymob Capture API
The Capture API from Paymob — 3 operation(s) for capture.
Paymob Checkout API
The Checkout API from Paymob — 1 operation(s) for checkout.
Paymob Disbursement API
The Disbursement API from Paymob — 4 operation(s) for disbursement.
Paymob Orders API
The Orders API from Paymob — 1 operation(s) for orders.
Paymob Payment Keys API
The Payment Keys API from Paymob — 1 operation(s) for payment keys.
Paymob Payment Links API
The Payment Links API from Paymob — 2 operation(s) for payment links.
Paymob Payments API
The Payments API from Paymob — 1 operation(s) for payments.
Paymob Refund API
The Refund API from Paymob — 3 operation(s) for refund.
Paymob Saved Card Payments API
The Saved Card Payments API from Paymob — 2 operation(s) for saved card payments.
Paymob Subscription Plans API
The Subscription Plans API from Paymob — 4 operation(s) for subscription plans.
Paymob Topup API
The Topup API from Paymob — 2 operation(s) for topup.
Paymob Transactions API
The Transactions API from Paymob — 2 operation(s) for transactions.
Paymob Void API
The Void API from Paymob — 3 operation(s) for void.
Scroll within the panel for all 18 ·
Open Collections 5
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).
Paymob Accept Legacy (v2) API
OPEN COLLECTIONPaymob Card Tokens API
OPEN COLLECTIONPaymob Intentions API
OPEN COLLECTIONPaymob Payouts (Send) API
OPEN COLLECTIONPaymob Subscriptions API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Paymob Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Paymob Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Paymob Finops
FINOPSFeatures 16
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.
Unified Checkout
Hosted, fully-branded checkout supporting all regional payment methods from a single integration.
Pixel
Embeddable checkout component for headless / custom-UI merchants.
Intentions API (v1)
Modern backend-first intention creation with client_secret hand-off and multiple payment methods per intention.
Quick Link
V2 sharable payment links for social, email, SMS, and WhatsApp collection flows.
Subscriptions Module
Plan and subscription management with suspend/resume/cancel and secondary card support.
Saved Cards (CIT / MIT)
Tokenised card storage and one-click / merchant-initiated transactions.
Installments / BNPL routing
Native routing to Tabby, Tamara, valU, Souhoola, Forsa, Aman across regional markets.
Marketplace Payouts
Split-payment and downstream payout automation for marketplaces and platforms.
Paymob Send (Payouts)
Mass disbursement to wallets, bank wallets, and bank cards with bulk and instant rails.
Paymob Sync
End-to-end cashless commerce platform combining acceptance, payouts, and reconciliation.
PCI-DSS certified infrastructure
Card data tokenised and stored in PCI-certified vaults; 3DS2 across regions.
Machine-learning fraud detection
Integrated risk engine scoring transactions in real time.
Real-time merchant dashboards
Per-region Accept dashboards for transactions, settlements, refunds, payouts.
Regional acquiring
Local entities in Egypt, KSA, UAE, Oman, Pakistan (Qatar announced) for in-country settlement.
Webhooks
HMAC-signed callbacks for transaction lifecycle, disbursement status, and subscription events.
Apple Pay, Google Pay, STC Pay, Oman Net, EasyPaisa, JazzCash
Native wallet integrations across MENAP markets.
Scroll within the panel for all 16 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Paymob Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Paymob API Rules
SPECTRALPaymob API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
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.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
E-commerce checkout
Online stores accepting cards, wallets, and BNPL across MENAP through a single integration.
SaaS subscription billing
Recurring billing for software and digital subscriptions with retry, suspend, and resume controls.
Ride-hailing and delivery payouts
Mass payouts to drivers and couriers via instant cashin (Vodafone Cash, Etisalat Cash, bank wallets).
Payroll and supplier disbursements
Bulk transfers to employees and suppliers across wallets and bank cards.
Marketplace split payments
Automated split between platform and sellers with downstream payout.
Bill payments and recurring collections
Subscription, utility, and installment collection across cards, wallets, and cash networks.
Omnichannel retail
POS terminals plus online acceptance unified through Paymob Sync for end-to-end commerce.
Cross-border MENAP expansion
Single contractual surface with regional acquiring across Egypt, KSA, UAE, Oman, Pakistan.
Scroll within the panel for all 8 ·
Integrations 14
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
WooCommerce
Official Accept Payments WooCommerce plugin.
Magento 2
Official Magento 2 plugin for Accept Payments.
OpenCart
Official OpenCart plugin.
Shopify
Paymob payment gateway available on Shopify.
Odoo
Paymob payment provider for Odoo 19.
OpenEduCat
School fee payment integration.
Xero
Xero backend integration repository.
Tabby
BNPL routing in KSA and UAE checkout.
Tamara
BNPL routing in KSA and UAE checkout.
valU / Souhoola / Forsa / Aman
Installment and cash-collection partners across Egypt.
Apple Pay / Google Pay
Native digital wallet acceptance across all live regions.
STC Pay
National wallet acceptance in Saudi Arabia.
Oman Net
Domestic acquiring in Oman.
EasyPaisa / JazzCash
Pakistani mobile wallet acceptance.
Scroll within the panel for all 14 ·
Solutions 5
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
SMB Standard
Self-serve onboarding with per-transaction pricing for startups, SMBs, and SMEs.
Enterprise
Custom MDR, dedicated account team, multi-region settlement, advanced fraud tooling.
Marketplace
Split payments, multi-merchant onboarding, and automated downstream payouts.
Platform / PSP
Sub-merchant onboarding and Paymob Sync for embedded payments.
Payouts-only
Standalone Send deployment for businesses that need mass disbursement without acceptance.
Resources
Every other property we hold for Paymob — 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 6
Portal, sign-up, and the first successful call
Documentation 7
Reference material describing how the API behaves
Scroll within the panel for all 7 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 14
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 14 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/paymob · machine-readable index on apis.io