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

44.4/100 thin ▬ flat Agent 80/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5

AccessSelf serve

2 APIs 1 MCP Servers

CompanyFintechPaymentsMobile PaymentsQR Code PaymentsDigital WalletJapanMerchant Payments

Kin Score

Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5

Composite quality — 44.4/100 · thin

Contract Quality 13.4 / 25

Developer Ergonomics 15.7 / 20

Commercial Clarity 2.6 / 20

Operational Transparency 4.8 / 13

Governance 0.0 / 12

Discoverability 9.3 / 10

Agent readiness — 80/100 · agent native

Machine-Readable Contract 18 / 18

Agentic Access Contract 15 / 15

MCP Server 12 / 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

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.

MCP Servers 1

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

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

MCPServer

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

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

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.20'
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/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

PayPay

Kin Score

APIs 2

PayPay Payment API

PayPay Payments API

MCP Servers 1

paypay-mcp.yml

Event Specifications 1

Paypay Webhooks

Security Posture 2

Paypay Authentication

Paypay Domain Security

Agentic Access 1

Paypay Agentic Access

Resources