Payple

Payple (페이플) is a South Korean payment gateway (PG) and fintech provider that lets merchants accept online payments across domestic and international cards, real-time bank-account payments, recurring / billing-key charges, link payments, identity verification, and settlement / payout (Hub) services. Integration is offered through a hosted payment window initialized in the browser with a public client key, plus a server-side REST API (v2) authorized with partner credentials (PCD_CST_ID / PCD_CUST_KEY). Payple is a registered Korean electronic financial business with an Innovative Financial Service (혁신금융서비스) designation, and it publishes official language sample source, policy documents, and a developer center. This profile was enriched by the API Evangelist pipeline from the Payple developer center and the PAYPLECORP GitHub organization.

Payple is listed with 1 API on the APIs.io network. Tagged areas include Company, Payments, Payment Gateway, Fintech, and South Korea.

The Payple catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Payple’s developer surface includes documentation, API reference, support, engineering blog, authentication, sandbox, and 19 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

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

1 API

Company Payments Payment Gateway Fintech South Korea Recurring Payments Billing Cards Bank Transfers

Kin Score

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

Composite quality — 40.7/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 10.1 / 17

Access Clarity 6.0 / 17

Operational Transparency 1.2 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 4.0 / 15

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 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 0 / 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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

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/payple/"><img src="https://apis.io/badge/payple/card.svg" alt="Payple 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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

8 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 39.0 — up to +15.3 composite points
Access Clarity scores 35.5 — up to +12.9 composite points
Operational Transparency scores 10.5 — up to +11.6 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/payple/apis.yml: open an issue on github.com/api-evangelist/payple 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
Korea MyData (licensed MyData operators, authentication bodies and information providers)	undeclared	-	-	1

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.

APIs 1

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

Payple Payment API

Payple REST payment API (v2) for card, bank-account, recurring/billing-key, link, verification, and payout (Hub) operations, plus the hosted payment window.

Event Specifications 1

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

Payple Webhooks

ASYNCAPI

Security Posture 2

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

Payple Authentication

3 schemes

SECURITY

Payple Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Idempotency

Lifecycle

Conformance

Webhooks

Components

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

DeclineCodes

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

Compliance

Compliance

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: payple
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - 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/payple.png
name: Payple
description: Payple (페이플) is a South Korean payment gateway (PG) and fintech provider that lets merchants accept online payments
  across domestic and international cards, real-time bank-account payments, recurring / billing-key charges, link payments,
  identity verification, and settlement / payout (Hub) services. Integration is offered through a hosted payment window initialized
  in the browser with a public client key, plus a server-side REST API (v2) authorized with partner credentials (PCD_CST_ID
  / PCD_CUST_KEY). Payple is a registered Korean electronic financial business with an Innovative Financial Service (혁신금융서비스)
  designation, and it publishes official language sample source, policy documents, and a developer center. This profile was
  enriched by the API Evangelist pipeline from the Payple developer center and the PAYPLECORP GitHub organization.
url: https://raw.githubusercontent.com/api-evangelist/payple/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Payments
- Payment Gateway
- Fintech
- South Korea
- Recurring Payments
- Billing
- Cards
- Bank Transfers
tags_raw:
- Company
- Payments
- Payment Gateway
- Fintech
- Korea
- Recurring Payments
- Billing
- Cards
- Bank Transfer
apis:
- name: Payple Payment API
  description: Payple REST payment API (v2) for card, bank-account, recurring/billing-key, link, verification, and payout
    (Hub) operations, plus the hosted payment window.
  humanURL: https://developer.payple.kr
  baseURL: https://api-v2.payple.kr
  tags:
  - Payments
  - Cards
  - Bank Transfers
  - Recurring Payments
  tags_raw:
  - Payments
  - Cards
  - Bank Transfer
  - Recurring Payments
  properties:
  - type: Documentation
    url: https://developer.payple.kr
  - type: APIReference
    url: https://developer.payple.kr/parameters/domestic-card/app
  - type: Authentication
    url: authentication/payple-authentication.yml
  - type: ErrorCatalog
    url: errors/payple-response-codes.yml
  - type: DeclineCodes
    url: errors/payple-decline-codes.yml
  - type: Sandbox
    url: sandbox/payple-sandbox.yml
  - type: Conventions
    url: conventions/payple-conventions.yml
  - type: Idempotency
    url: conventions/payple-conventions.yml
  - type: Lifecycle
    url: lifecycle/payple-lifecycle.yml
  - type: Webhooks
    url: asyncapi/payple-webhooks.yml
  - type: Components
    url: components/payple-components.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://payple.kr
- type: DeveloperPortal
  url: https://developer.payple.kr
- type: Documentation
  url: https://developer.payple.kr
- type: APIReference
  url: https://developer.payple.kr/parameters/domestic-card/app
- type: Support
  url: https://developer.payple.kr/faq
- type: GitHubOrganization
  url: https://github.com/PAYPLECORP
- type: Blog
  url: https://github.com/PAYPLECORP/Blog
- type: TermsOfService
  url: https://github.com/PAYPLECORP/policies
- type: PrivacyPolicy
  url: https://github.com/PAYPLECORP/policies
- type: Login
  url: https://accounts.payple.kr
- type: Packages
  url: packages/payple-packages.yml
- type: SDKs
  url: packages/payple-packages.yml
- type: Authentication
  url: authentication/payple-authentication.yml
- type: ErrorCatalog
  url: errors/payple-response-codes.yml
- type: DeclineCodes
  url: errors/payple-decline-codes.yml
- type: Sandbox
  url: sandbox/payple-sandbox.yml
- type: Conventions
  url: conventions/payple-conventions.yml
- type: Idempotency
  url: conventions/payple-conventions.yml
- type: Lifecycle
  url: lifecycle/payple-lifecycle.yml
- type: Conformance
  url: conformance/payple-conformance.yml
- type: Compliance
  url: conformance/payple-conformance.yml
- type: Webhooks
  url: asyncapi/payple-webhooks.yml
- type: Components
  url: components/payple-components.yml
- type: DomainSecurity
  url: security/payple-domain-security.yml
- type: LLMsTxt
  url: llms/payple-llms.txt
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 12
  pass: local-v1

Payple API — frequently asked questions

Does Payple have an API?

Yes. APIs.io lists 1 API from Payple, including Payple Payment API.

How do I authenticate with the Payple API?

Payple uses bearer-token authentication (3 schemes). The details are profiled on APIs.io as Payple Authentication.

Is the Payple API ready for AI agents?

Payple has a Kin Score of 40.7 out of 100 (developing) and an Agent Readiness score of 25.9 (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/payple"

All providers

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

Every operation they expose

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

How their score was established

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