PortOne
PortOne (formerly Iamport) is a Korea-based payment orchestration platform that lets online businesses integrate one API to reach 100+ Korean and global payment methods and PSPs. The V2 REST API (api.portone.io) covers payments, billing keys, scheduled/recurring payments, identity verification, cash receipts, B2B tax invoices, and partner settlement, with the legacy V1 API still served at api.iamport.kr.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles PortOne the way a machine reads it — 69 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — PortOne scores 59.1/100 (strong), with a separate agent-readiness read of 42/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from PortOne's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/portone/"
title="PortOne on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/portone.svg"
alt="PortOne Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/portone/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/portone/"
title="PortOne on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/portone/card.svg"
alt="PortOne Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile PortOne
Each block below is one kind of artifact we hold for PortOne. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
PortOne REST API (V1, legacy Iamport)
Legacy V1 (Iamport) REST API on api.iamport.kr — token-authenticated (POST /users/getToken with imp_key/imp_secret) payment lookup, cancellation, non-authenticated and scheduled...
PortOne B2b API
The B2b API from PortOne — 26 operation(s) for b2b.
PortOne Banks API
The Banks API from PortOne — 1 operation(s) for banks.
PortOne Billing Keys API
The Billing Keys API from PortOne — 4 operation(s) for billing keys.
PortOne Cash Receipts API
The Cash Receipts API from PortOne — 1 operation(s) for cash receipts.
PortOne Checkout Profiles API
The Checkout Profiles API from PortOne — 1 operation(s) for checkout profiles.
PortOne Identity Verifications API
The Identity Verifications API from PortOne — 5 operation(s) for identity verifications.
PortOne Kakaopay API
The Kakaopay API from PortOne — 1 operation(s) for kakaopay.
PortOne Login API
The Login API from PortOne — 1 operation(s) for login.
PortOne Payment Events By Cursor API
The Payment Events By Cursor API from PortOne — 1 operation(s) for payment events by cursor.
PortOne Payment Gateways API
The Payment Gateways API from PortOne — 1 operation(s) for payment gateways.
PortOne Payment Reconciliations API
The Payment Reconciliations API from PortOne — 2 operation(s) for payment reconciliations.
PortOne Payment Schedules API
The Payment Schedules API from PortOne — 2 operation(s) for payment schedules.
PortOne Payment Sessions API
The Payment Sessions API from PortOne — 3 operation(s) for payment sessions.
PortOne Payments API
The Payments API from PortOne — 18 operation(s) for payments.
PortOne Payments By Cursor API
The Payments By Cursor API from PortOne — 1 operation(s) for payments by cursor.
PortOne Paymentwall API
The Paymentwall API from PortOne — 1 operation(s) for paymentwall.
PortOne Platform API
The Platform API from PortOne — 44 operation(s) for platform.
PortOne Promotions API
The Promotions API from PortOne — 1 operation(s) for promotions.
PortOne Token API
The Token API from PortOne — 1 operation(s) for token.
Scroll within the panel for all 20 ·
Postman Collections 19
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
PortOne B2b API
POSTMANPortOne B2b Banks API
POSTMANPortOne B2b Billing Keys API
POSTMANPortOne B2b Kakaopay API
POSTMANPortOne B2b Login API
POSTMANPortOne B2b Payments API
POSTMANPortOne B2b Paymentwall API
POSTMANPortOne B2b Platform API
POSTMANPortOne B2b Promotions API
POSTMANPortOne B2b Token API
POSTMANScroll within the panel for all 19 ·
Open Collections 20
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONPortOne B2b API
OPEN COLLECTIONPortOne B2b Banks API
OPEN COLLECTIONPortOne B2b Billing Keys API
OPEN COLLECTIONPortOne B2b Cash Receipts API
OPEN COLLECTIONPortOne B2b Checkout Profiles API
OPEN COLLECTIONPortOne B2b Identity Verifications API
OPEN COLLECTIONPortOne B2b Kakaopay API
OPEN COLLECTIONPortOne B2b Login API
OPEN COLLECTIONPortOne B2b Payment Events By Cursor API
OPEN COLLECTIONPortOne B2b Payment Gateways API
OPEN COLLECTIONPortOne B2b Payment Reconciliations API
OPEN COLLECTIONPortOne B2b Payment Schedules API
OPEN COLLECTIONPortOne B2b Payment Sessions API
OPEN COLLECTIONPortOne B2b Payments API
OPEN COLLECTIONPortOne B2b Payments By Cursor API
OPEN COLLECTIONPortOne B2b Paymentwall API
OPEN COLLECTIONPortOne B2b Platform API
OPEN COLLECTIONPortOne B2b Promotions API
OPEN COLLECTIONPortOne B2b Token API
OPEN COLLECTIONScroll within the panel for all 20 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
PortOne MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Portone Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Portone Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Portone Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for PortOne — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/portone · machine-readable index on apis.io
This is an independent, third-party profile of PortOne, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.