Paga

Paga (Pagatech Financial Services Limited) is a Nigerian mobile-money and payments company founded in 2009 and licensed by the Central Bank of Nigeria. Its developer platform exposes REST APIs - the Business API, Collect API, and Direct Debit API - for disbursements, airtime/data and bill payments, bank deposits, and NGN collections via payment requests and persistent (NUBAN) account numbers. Authentication combines a principal/credential key pair with a per-request SHA-512 hash header.

Paga publishes 5 API contracts indexed on the APIs.io network, including Business API, Collect API, Direct Debit API, and 2 more. Tagged areas include Payments, Mobile Money, Fintech, Collection, and Nigeria.

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

Paga’s developer surface includes authentication, documentation, sandbox, quickstart, support, engineering blog, and 29 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

51.1/100 developing ▬ flat Agent 35/100 agent ready Front door AI 1/6 silent Heartbeat 0/100 dormant 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 Mobile Money Fintech Collection Nigeria

Kin Score

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

Composite quality — 51.1/100 · developing

Contract Quality 9.9 / 19

Developer Ergonomics 11.2 / 15

Access Clarity 4.7 / 15

Operational Transparency 4.1 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 5.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 35/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 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/paga/"><img src="https://apis.io/badge/paga/card.svg" alt="Paga 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
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)
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's

3 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 52.8 — up to +11.8 composite points
Contract Governance scores 18.2 — up to +9.8 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/paga/apis.yml: open an issue on github.com/api-evangelist/paga 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
African Payments (Nigeria, Kenya, South Africa, Ghana, WAEMU)	regulated	19.2 (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 5

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

Paga Connect

OAuth-based hosted checkout that lets third parties charge a customer's Paga wallet and read account/merchant details after the customer authorizes access. Documented separately...

Paga Business API

Disbursements, airtime/data, merchant payments, deposits, onboarding.

Paga Collect API

NGN collections - payment requests and persistent payment accounts.

Paga Direct Debit API

Bank-account mandate tokenization and recurring debits.

Paga Reference API

Look-up operations - banks, mobile operators, status.

Postman Collections 4

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

Paga Developer Business API

POSTMAN

Paga Developer Business Collect API

POSTMAN

Paga Developer Business Direct Debit API

POSTMAN

Paga Developer Business Reference API

POSTMAN

Open Collections 4

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

Paga Developer Business API

OPEN COLLECTION

Paga Developer Business Collect API

OPEN COLLECTION

Paga Developer Business Direct Debit API

OPEN COLLECTION

Paga Developer Business Reference API

OPEN COLLECTION

Agent Skills 4

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

Collect a payment with Paga

AGENT SKILL

Set up and charge a direct-debit mandate

AGENT SKILL

Disburse funds with the Paga Business API

AGENT SKILL

Issue a persistent payment account

AGENT SKILL

Paga API pricing

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

Plan	Price
Paga Business Account (API access) usage	—
Enterprise / Custom enterprise	—

Plan details, limits and sources →

Rate limits

Documented numeric limit: not published requests
IP whitelisting (Business API): whitelisted IPs only source ip

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

Pricing Plans 1

Published pricing tiers and plan structures.

Paga Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

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

Paga

SLA

FinOps 1

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

Paga Finops

FINOPS

Event Specifications 1

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

Paga Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

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

Paga Openapi Overlay

3 actions · update · paga-openapi.yml

DERIVED

Security Posture 4

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

Paga Authentication

http/apiKey · 4 schemes

SECURITY

Paga Domain Security

no transport/DNS hardening detected

SECURITY

Paga Vulnerability Disclosure

security.txt · contact published

SECURITY

Paga Trust Center

PCI DSS, CBN licensed (Mobile Money Operator), NDPR (Nigeria Data Protection Regulation)

SECURITY

Agentic Access 1

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

Paga Agentic Access

23 operations · 17 acting · 1 human-in-the-loop

23 operations · 17 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Sandbox

Sandbox

DeveloperPortal

DeveloperPortal

Quickstart

Quickstart

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Idempotency

Components

DataModel

Webhooks

Scroll for all 8

Build 4

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

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

StatusPage

StatusPage

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

TermsOfService

TermsOfService

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: paga
url: https://raw.githubusercontent.com/api-evangelist/paga/refs/heads/main/apis.yml
name: Paga
kind: company
description: Paga (Pagatech Financial Services Limited) is a Nigerian mobile-money and payments company founded in 2009 and
  licensed by the Central Bank of Nigeria. Its developer platform exposes REST APIs - the Business API, Collect API, and Direct
  Debit API - for disbursements, airtime/data and bill payments, bank deposits, and NGN collections via payment requests and
  persistent (NUBAN) account numbers. Authentication combines a principal/credential key pair with a per-request SHA-512 hash
  header.
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
  - url: https://www.paga.com/
    status: 302
    note: declared website redirects to https://www.mypaga.com/pagagroup/ — a different registrable domain (paga.com -> mypaga.com),
      possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/paga.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Payments
- Mobile Money
- Fintech
- Collection
- Nigeria
tags_raw:
- Payments
- Mobile Money
- Fintech
- Collections
- Nigeria
created: '2026-07-17'
modified: '2026-07-17'
specificationVersion: '0.23'
apis:
- aid: paga:paga-connect-api
  name: Paga Connect
  tags:
  - OAuth
  - Checkout
  - Payments
  - Authentication
  tags_raw:
  - OAuth
  - Checkout
  - Payments
  - Authentication
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer-docs.paga.com/docs/paga-connect
  baseURL: https://www.mypaga.com
  properties:
  - url: https://developer-docs.paga.com/docs/paga-connect
    type: Documentation
  description: OAuth-based hosted checkout that lets third parties charge a customer's Paga wallet and read account/merchant
    details after the customer authorizes access. Documented separately from the hash-authenticated REST surfaces.
- aid: paga:paga-business-api
  name: Paga Business API
  description: Disbursements, airtime/data, merchant payments, deposits, onboarding.
  humanURL: https://developer-docs.paga.com/docs/paga-collect-api
  baseURL: https://collect.paga.com
  tags:
  - Business
  properties:
  - type: OpenAPI
    url: openapi/paga-business-api-openapi.yml
  - type: Documentation
    url: https://developer-docs.paga.com/docs/paga-collect-api
  - type: APIReference
    url: https://developer-docs.paga.com/docs/operations-1
  - type: PostmanCollection
    url: collections/paga.postman_collection.json
  - type: Documentation
    url: https://developer-docs.paga.com/docs/business-rest-api
  - type: APIReference
    url: https://developer-docs.paga.com/docs/business-rest-api-operations
  - type: Documentation
    url: https://developer-docs.paga.com/docs/direct-debit-api
- aid: paga:paga-collect-api
  name: Paga Collect API
  description: NGN collections - payment requests and persistent payment accounts.
  humanURL: https://developer-docs.paga.com/docs/paga-collect-api
  baseURL: https://collect.paga.com
  tags:
  - Collect
  properties:
  - type: OpenAPI
    url: openapi/paga-collect-api-openapi.yml
  - type: Documentation
    url: https://developer-docs.paga.com/docs/paga-collect-api
  - type: APIReference
    url: https://developer-docs.paga.com/docs/operations-1
  - type: PostmanCollection
    url: collections/paga.postman_collection.json
  - type: Documentation
    url: https://developer-docs.paga.com/docs/business-rest-api
  - type: APIReference
    url: https://developer-docs.paga.com/docs/business-rest-api-operations
  - type: Documentation
    url: https://developer-docs.paga.com/docs/direct-debit-api
- aid: paga:paga-direct-debit-api
  name: Paga Direct Debit API
  description: Bank-account mandate tokenization and recurring debits.
  humanURL: https://developer-docs.paga.com/docs/paga-collect-api
  baseURL: https://collect.paga.com
  tags:
  - Direct Debit
  properties:
  - type: OpenAPI
    url: openapi/paga-direct-debit-api-openapi.yml
  - type: Documentation
    url: https://developer-docs.paga.com/docs/paga-collect-api
  - type: APIReference
    url: https://developer-docs.paga.com/docs/operations-1
  - type: PostmanCollection
    url: collections/paga.postman_collection.json
  - type: Documentation
    url: https://developer-docs.paga.com/docs/business-rest-api
  - type: APIReference
    url: https://developer-docs.paga.com/docs/business-rest-api-operations
  - type: Documentation
    url: https://developer-docs.paga.com/docs/direct-debit-api
- aid: paga:paga-reference-api
  name: Paga Reference API
  description: Look-up operations - banks, mobile operators, status.
  humanURL: https://developer-docs.paga.com/docs/paga-collect-api
  baseURL: https://collect.paga.com
  tags:
  - Reference
  properties:
  - type: OpenAPI
    url: openapi/paga-reference-api-openapi.yml
  - type: Documentation
    url: https://developer-docs.paga.com/docs/paga-collect-api
  - type: APIReference
    url: https://developer-docs.paga.com/docs/operations-1
  - type: PostmanCollection
    url: collections/paga.postman_collection.json
  - type: Documentation
    url: https://developer-docs.paga.com/docs/business-rest-api
  - type: APIReference
    url: https://developer-docs.paga.com/docs/business-rest-api-operations
  - type: Documentation
    url: https://developer-docs.paga.com/docs/direct-debit-api
common:
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/paga/overview
- type: AgenticAccess
  url: agentic-access/paga-agentic-access.yml
- type: TrustCenter
  url: security/paga-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/paga-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/paga-domain-security.yml
- type: Authentication
  url: authentication/paga-authentication.yml
- type: GitHubOrganization
  url: https://github.com/Paga-Developer-Community
- type: LinkedIn
  url: https://www.linkedin.com/company/paga-tech
- type: Website
  url: https://www.paga.com/
- type: Documentation
  url: https://developer-docs.paga.com/
- type: Plans
  url: plans/paga-plans-pricing.yml
- type: RateLimits
  url: rate-limits/paga-rate-limits.yml
- type: FinOps
  url: finops/paga-finops.yml
- type: Packages
  url: packages/paga-packages.yml
- type: SDKs
  url: packages/paga-packages.yml
- type: X-MCPServerCandidate
  url: mcp/paga-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/paga-llms.txt
- type: Overlay
  url: overlays/paga-openapi-overlay.yaml
- type: Conformance
  url: conformance/paga-conformance.yml
- type: Compliance
  url: security/paga-trust-center.yml
- type: ErrorCatalog
  url: errors/paga-error-codes.yml
- type: Lifecycle
  url: lifecycle/paga-lifecycle.yml
- type: StatusPage
  url: https://status.paga.com
- type: Sandbox
  url: sandbox/paga-sandbox.yml
- type: Conventions
  url: conventions/paga-conventions.yml
- type: Idempotency
  url: conventions/paga-conventions.yml
- type: Components
  url: components/paga-components.yml
- type: DataModel
  url: data-model/paga-data-model.yml
- type: Webhooks
  url: asyncapi/paga-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DeveloperPortal
  url: https://developer-docs.paga.com/
- type: Quickstart
  url: https://developer-docs.paga.com/docs/create-an-account
- type: Support
  url: https://www.paga.com/contact
- type: Blog
  url: https://paga.blog/
- type: TermsOfService
  url: https://www.paga.com/terms
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Paga API — frequently asked questions

Does Paga have an API?

Yes. APIs.io lists 5 APIs from Paga, including Paga Connect, Paga Business API and Paga Collect API, and 2 more.

Is there an OpenAPI specification for the Paga API?

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

How do I authenticate with the Paga API?

Paga uses bearer-token authentication (http/apiKey · 4 schemes). The details are profiled on APIs.io as Paga Authentication.

How much does the Paga API cost?

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

Is the Paga API ready for AI agents?

Paga has a Kin Score of 51.1 out of 100 (developing) and an Agent Readiness score of 34.9 (agent-ready), 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/paga"

All providers

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

Every operation they expose

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

How their score was established

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