PayTabs

PayTabs is a Saudi-built payment orchestration and gateway provider serving merchants across MENA. The PT2 REST API accepts cards and local methods (mada, Meeza, KNET, OmanNet, Benefit, STC Pay, urpay) plus Apple Pay, Google Pay and Samsung Pay through hosted, managed and own-form flows, with tokenization, recurring billing and invoicing. The API is served on region-specific hosts and authenticated with a merchant server key.

PayTabs publishes 2 API contracts indexed on the APIs.io network: Payments API and Transactions API. Tagged areas include Payments, Payment Gateway, Fintech, MENA, and Saudi Arabia.

The PayTabs catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

PayTabs’ developer surface includes authentication, documentation, engineering blog, getting-started guide, API reference, support, pricing, and 36 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

67.3/100 exemplar ▬ flat Agent 26/100 agent aware Heartbeat 94/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

1 published contract 3 Agent Skills

Payments Payment Gateway Fintech MENA Saudi Arabia Cards mada

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Consumer Commerce

AE-140

Payments

POST /payment/request

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 67.3/100 · exemplar

Contract Quality 10.4 / 19

Developer Ergonomics 11.7 / 15

Access Clarity 15.0 / 15

Operational Transparency 3.3 / 10

Contract Governance 2.9 / 9

Discoverability 5.0 / 8

Regulatory Posture 6.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/paytabs/"><img src="https://apis.io/badge/paytabs/card.svg" alt="PayTabs on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 55.2 — up to +11.2 composite points
Operational Transparency scores 34.2 — up to +8.6 composite points
Contract Governance scores 31.8 — up to +8.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/paytabs/apis.yml: open an issue on github.com/api-evangelist/paytabs to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Gulf and Southeast Asia Open Finance	distribution	9.6 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

PayTabs Payments API

Create and manage transactions.

PayTabs Transactions API

Query and manage existing transactions.

Postman Collections 2

Ready-to-run Postman collections for exercising this provider's APIs.

PayTabs PT2 Payments API

POSTMAN

PayTabs PT2 Payments Transactions API

POSTMAN

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

PayTabs PT2 Payments API

OPEN COLLECTION

PayTabs PT2 Payments Transactions API

OPEN COLLECTION

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Accept a hosted-page payment

AGENT SKILL

Query a transaction and refund it

AGENT SKILL

Tokenize a card and charge it recurringly

AGENT SKILL

PayTabs API pricing

Prices published by PayTabs, read 2026-10-28 from paytabs.com/en/pricing/.

Plan	Price
Paymes SuperApp Standalone App	SAR 49/ month Includes: Ready Online Store
SoftPOS Add-on	+SAR 20/ month Includes: Converts your phone on a terminal
Mada cards	Mada cards - 1%
Credit Cards	2.25% + SAR1
Payment Orchestration	Talk to Sales Includes: Whitelabel & Customization, Entire Payments Platform, Custom Setup inc. Sales & Operations, Data Loc

Plan details, limits and sources →

Rate limits

Request throughput: not publicly documented (risk/velocity managed) requests
Transaction velocity: risk-based transactions

Compiled by API Evangelist, not yet checked against PayTabs's documentation. Rate-limit details →

Billed by: transaction · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Paytabs Plans Pricing

5 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Paytabs Rate Limits

2 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

PayTabs

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Paytabs Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

PayTabs IPN / Callback Notifications

PayTabs delivers transaction outcomes to merchants via server-to-server HTTP POST notifications. There are two flavors of the same payload: the Callback (a one-time notification...

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

PayTabs API Rules

55 rules · 53 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Paytabs Openapi Overlay

4 actions · update · paytabs-openapi.yml

DERIVED

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Paytabs Authentication

apiKey · 2 schemes

SECURITY

Paytabs Domain Security

no transport/DNS hardening detected

SECURITY

Paytabs Vulnerability Disclosure

contact published

SECURITY

Paytabs Trust Center

PCI DSS Level 1, EMV 3-D Secure 2 (Modirum), mada / Saudi National Payment Gateway certified

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Paytabs Agentic Access

2 operations · 1 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

AsyncAPI

AsyncAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Idempotency

DataModel

Webhooks

Scroll for all 7

Build 6

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

GitHubOrganization

Postman

Packages

SDKs

DeclineCodes

Access & Security 6

Authentication, authorization, and security posture

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Authentication

Security

Compliance

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

StatusPage

StatusPage

Commercial 5

Pricing, plans, and the legal terms of use

Plans

FinOps

Pricing

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: paytabs
url: https://raw.githubusercontent.com/api-evangelist/paytabs/refs/heads/main/apis.yml
name: PayTabs
kind: company
description: PayTabs is a Saudi-built payment orchestration and gateway provider serving merchants across MENA. The PT2 REST
  API accepts cards and local methods (mada, Meeza, KNET, OmanNet, Benefit, STC Pay, urpay) plus Apple Pay, Google Pay and
  Samsung Pay through hosted, managed and own-form flows, with tokenization, recurring billing and invoicing. The API is served
  on region-specific hosts and authenticated with a merchant server key.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - plans
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/paytabs.png
tags:
- Payments
- Payment Gateway
- Fintech
- MENA
- Saudi Arabia
- Cards
- mada
created: '2026-07-17'
modified: '2026-07-17'
specificationVersion: '0.23'
apis:
- aid: paytabs:paytabs-payments-api
  name: PayTabs Payments API
  description: Create and manage transactions.
  humanURL: https://docs.paytabs.com/manuals/PT-API-Endpoints/Integration-Types-Manuals/Hosted-Payment-Page/HPP-Step-3-Initiating-Payment/HPP-Initiating-Payment/
  baseURL: https://secure.paytabs.com
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/paytabs-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.paytabs.com/manuals/PT-API-Endpoints/Introduction/
  - type: APIReference
    url: https://documenter.getpostman.com/view/14575178/TWDRtfWG
  - type: PostmanCollection
    url: collections/paytabs.postman_collection.json
  - type: Documentation
    url: https://docs.paytabs.com/manuals/PT-API-Endpoints/Integration-Types-Manuals/Hosted-Payment-Page/HPP-Step-7-Manage-Transactions/HPP-Step-7-Query-Transaction/
  - type: Documentation
    url: https://docs.paytabs.com/manuals/PT-API-Endpoints/Repeat-Billing/Step-1-Understanding-Workflow-&-Prerequisites/Repeat-Billing-Prerequisites/
  - type: Documentation
    url: https://support.paytabs.com/en/support/solutions/articles/60000902481-3-2-3-invoices-apis-initiating-the-payment-request-download-invoice-pdf
- aid: paytabs:paytabs-transactions-api
  name: PayTabs Transactions API
  description: Query and manage existing transactions.
  humanURL: https://docs.paytabs.com/manuals/PT-API-Endpoints/Integration-Types-Manuals/Hosted-Payment-Page/HPP-Step-3-Initiating-Payment/HPP-Initiating-Payment/
  baseURL: https://secure.paytabs.com
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/paytabs-transactions-api-openapi.yml
  - type: Documentation
    url: https://docs.paytabs.com/manuals/PT-API-Endpoints/Introduction/
  - type: APIReference
    url: https://documenter.getpostman.com/view/14575178/TWDRtfWG
  - type: PostmanCollection
    url: collections/paytabs.postman_collection.json
  - type: Documentation
    url: https://docs.paytabs.com/manuals/PT-API-Endpoints/Integration-Types-Manuals/Hosted-Payment-Page/HPP-Step-7-Manage-Transactions/HPP-Step-7-Query-Transaction/
  - type: Documentation
    url: https://docs.paytabs.com/manuals/PT-API-Endpoints/Repeat-Billing/Step-1-Understanding-Workflow-&-Prerequisites/Repeat-Billing-Prerequisites/
  - type: Documentation
    url: https://support.paytabs.com/en/support/solutions/articles/60000902481-3-2-3-invoices-apis-initiating-the-payment-request-download-invoice-pdf
common:
- type: CapabilityMap
  url: capabilities/paytabs-capability-edges.yml
  name: PayTabs Business Capability Map
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/paytabs/overview
- type: AgenticAccess
  url: agentic-access/paytabs-agentic-access.yml
- type: TrustCenter
  url: security/paytabs-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/paytabs-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/paytabs-domain-security.yml
- type: Authentication
  url: authentication/paytabs-authentication.yml
- type: GitHubOrganization
  url: https://github.com/paytabscom
- type: LinkedIn
  url: https://www.linkedin.com/company/paytabs
- type: Website
  url: https://paytabs.com/en/
- type: Documentation
  url: https://docs.paytabs.com/
- type: Plans
  url: plans/paytabs-plans-pricing.yml
- type: RateLimits
  url: rate-limits/paytabs-rate-limits.yml
- type: FinOps
  url: finops/paytabs-finops.yml
- url: https://paytabs.com/news/
  type: Blog
- type: DeveloperPortal
  url: https://docs.paytabs.com/
- type: GettingStarted
  url: https://docs.paytabs.com/PT2-API-Endpoints/Introduction/
- type: APIReference
  url: https://documenter.getpostman.com/view/14575178/TWDRtfWG
- type: Postman
  url: https://documenter.getpostman.com/view/14575178/TWDRtfWG
- type: Support
  url: https://support.paytabs.com/en/support/home
- type: Pricing
  url: https://paytabs.com/en/pricing/
- type: SignUp
  url: https://merchant.paytabs.com/merchant/register
- type: TermsOfService
  url: https://ai.paytabs.com/en/terms-of-use/
- type: PrivacyPolicy
  url: https://ai.paytabs.com/en/privacy-policy/
- type: StatusPage
  url: https://status.paytabs.com/
- type: Security
  url: https://ai.paytabs.com/en/security-compliance/
- type: Compliance
  url: https://ai.paytabs.com/en/security-compliance/
- type: Packages
  url: packages/paytabs-packages.yml
- type: SDKs
  url: packages/paytabs-packages.yml
- type: X-MCPServerCandidate
  url: mcp/paytabs-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/paytabs-llms.txt
- type: Overlay
  url: overlays/paytabs-openapi-overlay.yaml
- type: Conformance
  url: conformance/paytabs-conformance.yml
- type: ErrorCatalog
  url: errors/paytabs-problem-types.yml
- type: DeclineCodes
  url: errors/paytabs-decline-codes.yml
- type: Lifecycle
  url: lifecycle/paytabs-lifecycle.yml
- type: Conventions
  url: conventions/paytabs-conventions.yml
- type: Idempotency
  url: conventions/paytabs-conventions.yml
- type: DataModel
  url: data-model/paytabs-data-model.yml
- type: AsyncAPI
  url: asyncapi/paytabs-webhooks-asyncapi.yml
- type: Webhooks
  url: asyncapi/paytabs-webhooks-asyncapi.yml
- type: Sandbox
  url: sandbox/paytabs-sandbox.yml
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

PayTabs API — frequently asked questions

Does PayTabs have an API?

Yes. APIs.io lists 2 APIs from PayTabs, including PayTabs Payments API and PayTabs Transactions API.

Is there an OpenAPI specification for the PayTabs API?

Yes. APIs.io indexes 2 OpenAPI specifications for PayTabs, each linked for download from this page.

How do I authenticate with the PayTabs API?

PayTabs uses bearer-token authentication (apiKey · 2 schemes). The details are profiled on APIs.io as Paytabs Authentication.

How much does the PayTabs API cost?

PayTabs publishes its prices; its Paymes SuperApp Standalone App plan is SAR 49/ month as of 2026-10-28. APIs.io lists 5 pricing plans for PayTabs, with each plan's price, limits and inclusions under Pricing on this page.

Is the PayTabs API ready for AI agents?

PayTabs has a Kin Score of 67.3 out of 100 (exemplar) and an Agent Readiness score of 26.0 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/paytabs"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/paytabs/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/paytabs/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.