PayPay website screenshot

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

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

🌐 Visit website 📡 Source on GitHub
38.1/100 thin ▬ flat Agent 45/100 agent ready Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
AccessSelf serve
2 APIs 1 MCP Servers
CompanyFintechPaymentsMobile PaymentsQR Code PaymentsDigital WalletJapanMerchant Payments

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 38.1/100 · thin
Contract Quality 11.9 / 21
Developer Ergonomics 8.4 / 17
Access Clarity 0.0 / 17
Operational Transparency 3.8 / 11
Contract Governance 1.7 / 10
Discoverability 7.4 / 9
Regulatory Posture 4.0 / 15
Agent readiness — 45/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 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
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.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/paypay: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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 3

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

API Collection

OPEN COLLECTION

Dynamic QR Payment API

OPEN COLLECTION

Dynamic QR Payment Payments API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

PayPay MCP Server

MCP SERVER

Event Specifications 1

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

Paypay Webhooks

ASYNCAPI

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

10 operations · 7 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 SignUp
SignUp
 Sandbox
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

MCPServer
MCPServer
 AgentSkill
AgentSkill
 LLMsTxt
LLMsTxt
 AgenticAccess
AgenticAccess

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Idempotency
Idempotency
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 DataModel
DataModel
 Webhooks
Webhooks
 Conformance
Conformance

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages
 SDKs
SDKs
 DeclineCodes
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

Other 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: paypay
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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-07-20'
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:
  - 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:
- 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: MCPServer
  url: mcp/paypay-mcp.yml
- 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