HyperPay

HyperPay is a MENA / Saudi Arabia online payment gateway built on the ACI / OPPWA Open Payment Platform. Its REST API powers the COPYandPAY hosted widget and a Server-to-Server integration, accepting cards (VISA, MASTER, AMEX), the Saudi domestic mada scheme, STC Pay, and Apple Pay, priced and settled in SAR. Additional products include HyperSplit (marketplace payouts) and HyperBill (invoicing).

HyperPay publishes 6 API contracts indexed on the APIs.io network, including COPYandPAY API, Payments API, Query API, and 3 more. Tagged areas include Payments, Payment Gateway, Fintech, MENA, and Saudi Arabia.

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

HyperPay’s developer surface includes authentication, documentation, engineering blog, API reference, getting-started guide, support, sandbox, and 29 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

52.6/100 developing ▬ flat Agent 28/100 agent aware Front door AI 2/6 trace saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

1 published contract 4 Agent Skills

Payments Payment Gateway Fintech MENA Saudi Arabia mada Apple Pay Cards

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

COPYandPAY

Kin Score

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

Composite quality — 52.6/100 · developing

Contract Quality 10.2 / 19

Developer Ergonomics 11.2 / 15

Access Clarity 4.7 / 15

Operational Transparency 3.1 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 6.2 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 28/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 0 / 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/hyperpay/"><img src="https://apis.io/badge/hyperpay/card.svg" alt="HyperPay 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
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
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)

6 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 31.6 — up to +13.7 composite points
Contract Quality scores 54.3 — up to +11.4 composite points
Operational Transparency scores 31.6 — up to +8.9 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/hyperpay/apis.yml: open an issue on github.com/api-evangelist/hyperpay 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	undeclared	-	-	-

Not yet checked against HyperPay's own pricing page. Compiled by API Evangelist on 2026-07-17 from www.hyperpay.com/; confirm before you rely on a figure.

Plan	Price
Standard Merchant (quote-based) subscription	—
Enterprise (negotiated) enterprise	—

Plan details, limits and sources →

Rate limits

Per-channel transaction throughput: see provider / account manager transactions
Velocity / anti-fraud controls: risk-based transactions

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

Pricing Plans 1

Published pricing tiers and plan structures.

Hyperpay Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Hyperpay 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.

HyperPay

SLA

FinOps 1

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

Hyperpay Finops

FINOPS

Event Specifications 1

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

Hyperpay Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

HyperPay API Rules

60 rules · 58 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.

Hyperpay Openapi Overlay

4 actions · update · hyperpay-openapi.yml

DERIVED

Security Posture 4

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

Hyperpay Authentication

http · 2 schemes

SECURITY

Hyperpay Domain Security

HSTS

SECURITY

Hyperpay Vulnerability Disclosure

security.txt · contact published

SECURITY

Hyperpay Trust Center

PCI-DSS Level 1, SAMA (Saudi Central Bank) licensed payment service provider

SECURITY

Agentic Access 1

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

Hyperpay Agentic Access

9 operations · 6 acting · 5 human-in-the-loop

9 operations · 6 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

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

Components

DataModel

Webhooks

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

Packages

SDKs

DeclineCodes

Access & Security 5

Authentication, authorization, and security posture

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Deprecation

Deprecation

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

LinkedIn

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: hyperpay
url: https://raw.githubusercontent.com/api-evangelist/hyperpay/refs/heads/main/apis.yml
name: HyperPay
kind: company
description: HyperPay is a MENA / Saudi Arabia online payment gateway built on the ACI / OPPWA Open Payment Platform. Its
  REST API powers the COPYandPAY hosted widget and a Server-to-Server integration, accepting cards (VISA, MASTER, AMEX), the
  Saudi domestic mada scheme, STC Pay, and Apple Pay, priced and settled in SAR. Additional products include HyperSplit (marketplace
  payouts) and HyperBill (invoicing).
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/hyperpay.png
tags:
- Payments
- Payment Gateway
- Fintech
- MENA
- Saudi Arabia
- mada
- Apple Pay
- Cards
created: '2026-07-17'
modified: '2026-07-18'
specificationVersion: '0.23'
apis:
- aid: hyperpay:hyperpay-hypersplit
  name: HyperPay HyperSplit
  tags:
  - Payouts
  - Marketplace
  - Split Payments
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.hyperpay.com/hypersplit/
  baseURL: https://www.hyperpay.com/hypersplit/
  properties:
  - url: https://www.hyperpay.com/hypersplit/
    type: Documentation
  description: HyperSplit distributes a single collected payment across multiple sub-merchants or beneficiaries for marketplace
    and platform payout scenarios. Onboarding and API access are arranged with a HyperPay account manager.
- aid: hyperpay:hyperpay-hyperbill
  name: HyperPay HyperBill
  tags:
  - Invoicing
  - Payment Links
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.hyperpay.com/hyperbill/
  baseURL: https://www.hyperpay.com/hyperbill/
  properties:
  - url: https://www.hyperpay.com/hyperbill/
    type: Documentation
  description: HyperBill issues invoices and shareable payment links that collect payment through the HyperPay platform without
    a custom checkout integration.
- aid: hyperpay:hyperpay-copyandpay-api
  name: HyperPay COPYandPAY API
  description: Hosted widget checkout preparation and result.
  humanURL: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
  baseURL: https://eu-prod.oppwa.com/v1
  tags:
  - COPYandPAY
  properties:
  - type: OpenAPI
    url: openapi/hyperpay-copyandpay-api-openapi.yml
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
  - type: APIReference
    url: https://hyperpay.docs.oppwa.com/reference/parameters
  - type: PostmanCollection
    url: collections/hyperpay.postman_collection.json
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/server-to-server
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/manage-payments/registration
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/reporting
- aid: hyperpay:hyperpay-payments-api
  name: HyperPay Payments API
  description: Server-to-Server payments and back-office operations.
  humanURL: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
  baseURL: https://eu-prod.oppwa.com/v1
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/hyperpay-payments-api-openapi.yml
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
  - type: APIReference
    url: https://hyperpay.docs.oppwa.com/reference/parameters
  - type: PostmanCollection
    url: collections/hyperpay.postman_collection.json
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/server-to-server
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/manage-payments/registration
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/reporting
- aid: hyperpay:hyperpay-query-api
  name: HyperPay Query API
  description: Query the status of a prior payment.
  humanURL: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
  baseURL: https://eu-prod.oppwa.com/v1
  tags:
  - Query
  properties:
  - type: OpenAPI
    url: openapi/hyperpay-query-api-openapi.yml
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
  - type: APIReference
    url: https://hyperpay.docs.oppwa.com/reference/parameters
  - type: PostmanCollection
    url: collections/hyperpay.postman_collection.json
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/server-to-server
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/manage-payments/registration
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/reporting
- aid: hyperpay:hyperpay-registrations-api
  name: HyperPay Registrations API
  description: Tokenization of payment instruments for one-click and recurring.
  humanURL: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
  baseURL: https://eu-prod.oppwa.com/v1
  tags:
  - Registrations
  properties:
  - type: OpenAPI
    url: openapi/hyperpay-registrations-api-openapi.yml
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
  - type: APIReference
    url: https://hyperpay.docs.oppwa.com/reference/parameters
  - type: PostmanCollection
    url: collections/hyperpay.postman_collection.json
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/server-to-server
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/manage-payments/registration
  - type: Documentation
    url: https://hyperpay.docs.oppwa.com/tutorials/reporting
common:
- type: CapabilityMap
  url: capabilities/hyperpay-capability-edges.yml
  name: HyperPay Business Capability Map
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/hyperpay/overview
- type: AgenticAccess
  url: agentic-access/hyperpay-agentic-access.yml
- type: TrustCenter
  url: security/hyperpay-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/hyperpay-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/hyperpay-domain-security.yml
- type: Authentication
  url: authentication/hyperpay-authentication.yml
- type: Website
  url: https://www.hyperpay.com/
- type: Documentation
  url: https://hyperpay.docs.oppwa.com/
- type: LinkedIn
  url: https://www.linkedin.com/company/hyperpay
- type: Plans
  url: plans/hyperpay-plans-pricing.yml
- type: RateLimits
  url: rate-limits/hyperpay-rate-limits.yml
- type: FinOps
  url: finops/hyperpay-finops.yml
- url: https://www.hyperpay.com/blog/
  type: Blog
- type: DeveloperPortal
  url: https://hyperpay.docs.oppwa.com/
- type: APIReference
  url: https://hyperpay.docs.oppwa.com/reference/parameters
- type: GettingStarted
  url: https://hyperpay.docs.oppwa.com/tutorials/integration-guide
- type: Support
  url: https://www.hyperpay.com/contact/
- type: PrivacyPolicy
  url: https://www.hyperpay.com/privacy-policy/
- type: Packages
  url: packages/hyperpay-packages.yml
- type: SDKs
  url: packages/hyperpay-packages.yml
- type: X-MCPServerCandidate
  url: mcp/hyperpay-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/hyperpay-llms.txt
- type: Overlay
  url: overlays/hyperpay-openapi-overlay.yaml
- type: Conformance
  url: conformance/hyperpay-conformance.yml
- type: Compliance
  url: security/hyperpay-trust-center.yml
- type: ErrorCatalog
  url: errors/hyperpay-result-codes.yml
- type: DeclineCodes
  url: errors/hyperpay-decline-codes.yml
- type: Lifecycle
  url: lifecycle/hyperpay-lifecycle.yml
- type: Deprecation
  url: lifecycle/hyperpay-lifecycle.yml
- type: Sandbox
  url: sandbox/hyperpay-sandbox.yml
- type: Conventions
  url: conventions/hyperpay-conventions.yml
- type: Components
  url: components/hyperpay-components.yml
- type: DataModel
  url: data-model/hyperpay-data-model.yml
- type: Webhooks
  url: asyncapi/hyperpay-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

HyperPay API — frequently asked questions

Does HyperPay have an API?

Yes. APIs.io lists 6 APIs from HyperPay, including HyperPay HyperSplit, HyperPay HyperBill and HyperPay COPYandPAY API, and 3 more.

Is there an OpenAPI specification for the HyperPay API?

Yes. APIs.io indexes 4 OpenAPI specifications for HyperPay, each linked for download from this page.

How do I authenticate with the HyperPay API?

HyperPay uses bearer-token authentication (http · 2 schemes). The details are profiled on APIs.io as Hyperpay Authentication.

How much does the HyperPay API cost?

APIs.io lists 2 pricing plans for HyperPay, with each plan's price, limits and inclusions under Pricing on this page.

Is the HyperPay API ready for AI agents?

HyperPay has a Kin Score of 52.6 out of 100 (developing) and an Agent Readiness score of 27.6 (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/hyperpay"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/hyperpay/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.