PayPay

PayPay is Japan's largest QR/barcode mobile-payment network (a SoftBank / Yahoo Japan / Paytm joint venture) with tens of millions of users. Its Open Payment API (OPA v2) lets payment partners and merchants collect payments from PayPay wallet users through dynamic QR codes, web checkout (Web Cashier), app-invoke deep links, and a pre-authorize-and-capture flow. The REST API (base //apigw.paypay.ne.jp) is secured with HMAC-SHA256 request signatures, settles in JPY, sends transaction webhooks plus daily reconciliation files, and ships official Node, PHP, Python and Java SDKs under the github.com/paypay organization.

PayPay publishes 2 API contracts indexed on the APIs.io network: Payment API and Payments API. Tagged areas include Company, Fintech, Payments, Mobile Payments, and QR Code Payments.

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

PayPay’s developer surface includes documentation, API reference, getting-started guide, signup flow, support, authentication, changelog, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.5/100 thin ▬ flat Agent 32/100 agent ready Front door AI 1/6 silent Heartbeat 28/100 slowing saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company Fintech Payments Mobile Payments QR Code Payments Digital Wallet Japan Merchant Payments

What this lets a business do 1

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

Subscription Billing & Revenue Management

BC-4250

Payment

POST /v2/codes POST /v2/payments/capture POST /v2/refunds

Kin Score

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

Composite quality — 35.5/100 · thin

Contract Quality 9.8 / 19

Developer Ergonomics 7.4 / 15

Access Clarity 0.0 / 15

Operational Transparency 3.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 32/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 0 / 7

Rate-Limit Signaling 0 / 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/paypay/"><img src="https://apis.io/badge/paypay/card.svg" alt="PayPay 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
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
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)

5 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 0.0 — up to +20.0 composite points
Contract Quality scores 52.1 — up to +12.0 composite points
Developer Ergonomics scores 49.4 — up to +10.1 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/paypay/apis.yml: open an issue on github.com/api-evangelist/paypay 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
Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification)	regulated	50.3	-	-
Japan FSA Registered Fintech (crypto exchanges, stablecoin intermediaries, funds transfer, bank-API agents, prepaid)	regulated	50.3	-	-
Official SDKs on Packagist, pub.dev and Hex	regulated	50.3	-	-

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.

PayPay Payment API

Everything involved in the payment life cycle

PayPay Payments API

The Payments API from PayPay — 1 operation(s) for payments.

Open Collections 2

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

Dynamic QR Payment API

OPEN COLLECTION

Dynamic QR Payment Payments API

OPEN COLLECTION

Agent Skills 2

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

Collect a payment with a PayPay dynamic QR code

AGENT SKILL

Pre-authorize and capture a PayPay payment

AGENT SKILL

Event Specifications 1

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

Paypay Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

PayPay API Rules

46 rules · 38 errors 7 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.

Paypay Opa Overlay

1 action · update · paypay-opa-openapi-original.json

DERIVED

Security Posture 2

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

Paypay Authentication

http/hmac · 2 schemes

SECURITY

Paypay Domain Security

TLSv1.3

SECURITY

Agentic Access 1

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

Paypay Agentic Access

10 operations · 7 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

OpenAPI

OpenAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgentSkill

LLMsTxt

AgenticAccess

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

DataModel

Webhooks

Conformance

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

DeclineCodes

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

Deprecation

Deprecation

ChangeLog

ChangeLog

Company 2

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: paypay
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/paypay.png
name: PayPay
description: PayPay is Japan's largest QR/barcode mobile-payment network (a SoftBank / Yahoo Japan / Paytm joint venture)
  with tens of millions of users. Its Open Payment API (OPA v2) lets payment partners and merchants collect payments from
  PayPay wallet users through dynamic QR codes, web checkout (Web Cashier), app-invoke deep links, and a pre-authorize-and-capture
  flow. The REST API (base //apigw.paypay.ne.jp) is secured with HMAC-SHA256 request signatures, settles in JPY, sends transaction
  webhooks plus daily reconciliation files, and ships official Node, PHP, Python and Java SDKs under the github.com/paypay
  organization.
url: https://raw.githubusercontent.com/api-evangelist/paypay/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- softbank-vision-fund
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Fintech
- Payments
- Mobile Payments
- QR Code Payments
- Digital Wallet
- Japan
- Merchant Payments
apis:
- aid: paypay:paypay-payment-api
  name: PayPay Payment API
  description: Everything involved in the payment life cycle
  humanURL: https://developer.paypay.ne.jp/
  baseURL: https://apigw.paypay.ne.jp
  tags:
  - Payments
  tags_raw:
  - Payment
  properties:
  - type: OpenAPI
    url: openapi/paypay-payment-api-openapi.yml
  - type: APIReference
    url: https://www.paypay.ne.jp/opa/doc/v1.0/dynamicqrcode
- aid: paypay:paypay-payments-api
  name: PayPay Payments API
  description: The Payments API from PayPay — 1 operation(s) for payments.
  humanURL: https://developer.paypay.ne.jp/
  baseURL: https://apigw.paypay.ne.jp
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/paypay-payments-api-openapi.yml
  - type: APIReference
    url: https://www.paypay.ne.jp/opa/doc/v1.0/dynamicqrcode
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://blog.paypay.ne.jp/feed/
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/paypay-capability-edges.yml
  name: PayPay Business Capability Map
- type: Website
  url: https://paypay.ne.jp
- type: DeveloperPortal
  url: https://developer.paypay.ne.jp/
- type: Documentation
  url: https://www.paypay.ne.jp/opa/doc/v1.0/dynamicqrcode
- type: APIReference
  url: https://www.paypay.ne.jp/opa/doc/v1.0/dynamicqrcode
- type: GettingStarted
  url: https://developer.paypay.ne.jp/
- type: SignUp
  url: https://developer.paypay.ne.jp/
- type: Support
  url: https://integration.paypay.ne.jp/hc/en-us
- type: GitHubOrganization
  url: https://github.com/paypay
- type: OpenAPI
  url: openapi/_original/paypay-opa-openapi-original.json
- type: Overlay
  url: overlays/paypay-opa-overlay.yaml
- type: Authentication
  url: authentication/paypay-authentication.yml
- type: Packages
  url: packages/paypay-packages.yml
- type: SDKs
  url: packages/paypay-packages.yml
- type: Conventions
  url: conventions/paypay-conventions.yml
- type: Idempotency
  url: conventions/paypay-conventions.yml
- type: ErrorCatalog
  url: errors/paypay-problem-types.yml
- type: DeclineCodes
  url: errors/paypay-decline-codes.yml
- type: Lifecycle
  url: lifecycle/paypay-lifecycle.yml
- type: Deprecation
  url: lifecycle/paypay-lifecycle.yml
- type: ChangeLog
  url: changelog/paypay-changelog.yml
- type: DataModel
  url: data-model/paypay-data-model.yml
- type: Webhooks
  url: asyncapi/paypay-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/paypay-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: Conformance
  url: conformance/paypay-conformance.yml
- type: Sandbox
  url: sandbox/paypay-sandbox.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/paypay-llms.txt
- type: DomainSecurity
  url: security/paypay-domain-security.yml
- type: AgenticAccess
  url: agentic-access/paypay-agentic-access.yml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 19
  pass: local-v1

PayPay API — frequently asked questions

Does PayPay have an API?

Yes. APIs.io lists 2 APIs from PayPay, including PayPay Payment API and PayPay Payments API.

Is there an OpenAPI specification for the PayPay API?

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

How do I authenticate with the PayPay API?

PayPay uses bearer-token authentication (http/hmac · 2 schemes). The details are profiled on APIs.io as Paypay Authentication.

Is the PayPay API ready for AI agents?

PayPay has a Kin Score of 35.5 out of 100 (thin) and an Agent Readiness score of 31.8 (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/paypay"

All providers

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

Every operation they expose

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

How their score was established

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