PortOne Asia Payment Orchestration API
PortOne (formerly iamport) Asia payment orchestration REST API for merchants to integrate multiple Asian payment providers (Korea PGs, SEA gateways, Japan, Taiwan) through a unified API with a single integration supporting 200+ payment methods across Asia. Enables AI agents to manage unified payment transaction creation across Asian payment providers for multi-country Asia payment automation, handle Korea domestic payment gateway routing for Korean market automation, access Southeast Asia payment method routing for regional payment automation, retrieve payment reconciliation across multiple Asian providers for cross-market financial automation, manage subscription and recurring billing across Asian payment systems for Asia subscription automation, handle refund processing across payment providers for Asia order management automation, access payment analytics and reporting for Asia commerce performance automation, retrieve webhook unification from multiple payment providers for consolidated event automation, manage payment method selection and routing logic for Asia payment optimization automation, and integrate PortOne with Asian e-commerce platforms and business systems for end-to-end Asia payment orchestration.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Asia payment orchestration. PCI-DSS. API key/OAuth. KR/SG. Payment data.
⚡ Reliability
Best When
A merchant selling across multiple Asian markets wanting AI agents to automate multi-PG payment routing, payment method selection, and reconciliation through PortOne's unified Asia payment orchestration API.
Avoid When
PAYMENT GATEWAY CREDENTIALS REQUIRED PER PROVIDER: PortOne orchestrates payment providers but requires merchant credentials for each underlying payment provider (KG Inicis, Toss, NHN KCP, etc.); automated payment setup requires coordinating merchant accounts with multiple PGs; automated PortOne-without-PG-credentials integration fails at payment routing despite PortOne API access. PAYMENT PROVIDER ROUTING LOGIC REQUIRES CONFIGURATION: PortOne's payment provider routing is configured per merchant account; automated payment routing depends on configured provider priority and fallback rules; automated payment without routing configuration defaults to primary provider without intelligent failover. API VERSIONING DURING REBRAND: PortOne rebranded from iamport; automated integrations must use current PortOne API endpoints; automated legacy iamport endpoint usage may encounter deprecation or routing changes as migration completes.
Use Cases
- • Orchestrating payments across Asian markets from unified payment agents
- • Integrating Korean PGs through single API from Korean payment agents
- • Routing SEA payments from Southeast Asia commerce agents
- • Consolidating Asian payment reporting from financial reconciliation agents
Not For
- • Europe-only payment processing (use Adyen or Stripe for European focus)
- • LATAM payments (use Mercado Pago or PayU for Latin America)
- • Simple single-country Asia payment (use country-specific processor for single-market simplicity)
Interface
Authentication
PortOne uses API key and OAuth 2.0 for integrations. REST API with JSON. Seoul, South Korea and Singapore dual HQ. Founded 2019 (as iamport in 2013). Backed by SoftBank Ventures, Kakao Ventures, Square Peg ($50M+ raised). Products: Asia payment orchestration, 200+ payment methods, Korea PG aggregation, SEA routing, Japan/Taiwan. SDKs: JavaScript, Java, PHP, Python, Ruby, Go. PCI DSS. Serves 80,000+ merchants across Asia. Competes with Adyen, Checkout.com, and country-specific processors for Asia payment orchestration.
Pricing
Seoul KR / Singapore SG. SoftBank Ventures backed. Pass-through + platform fee model. Custom enterprise pricing.
Agent Metadata
Known Gotchas
- ⚠ PG PROVIDER CODE REQUIRED FOR PAYMENT ROUTING: PortOne payment requests require PG (payment gateway) provider code to route to correct underlying provider; automated payment must specify pg_provider field; automated payment without pg_provider creates default provider routing which may not match intended payment method
- ⚠ IAMPORT TO PORTONE API ENDPOINT MIGRATION: PortOne rebranded from iamport; some documentation and examples reference legacy api.iamport.kr endpoints; automated integration should use current PortOne API endpoint; automated legacy endpoint usage may encounter rate limits or deprecation as migration progresses
- ⚠ PAYMENT FLOW TWO-STEP AUTHENTICATION: PortOne payments require client-side initiation (with IMP.request_pay) followed by server-side verification (with payment ID); automated payment flow must implement both steps; automated server-side-only payment misses required client-side authentication
- ⚠ MULTI-CURRENCY SETTLEMENT VARIES BY PROVIDER: Each underlying payment provider settles in different currency and timeline; automated financial reconciliation must account for provider-specific settlement currency and timing; automated unified settlement report requires currency conversion for cross-market comparison
- ⚠ WEBHOOK SIGNATURE VERIFICATION PER PROVIDER: PortOne webhooks include provider-specific signatures; automated webhook processing must verify signature; unverified webhook processing creates security risk from spoofed payment events
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for PortOne Asia Payment Orchestration API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.