KakaoPay Korea Digital Wallet API
KakaoPay Korea digital wallet REST API for Korean e-commerce merchants, apps, and service providers to accept payments from 37M+ KakaoPay users directly through KakaoTalk messaging app authentication, enabling one-tap checkout, subscription billing, easy pay with registered cards, loyalty points, and investment savings accounts integrated with Korea's dominant mobile platform. Enables AI agents to manage KakaoPay checkout for Korean mobile payment automation, handle subscription billing for recurring Korean payment automation, access payment approval for one-tap purchase automation, retrieve payment cancellation for Korean order reversal automation, manage ready payment for pre-authorized subscription automation, handle loyalty point integration for reward redemption automation, access payment status inquiry for transaction verification automation, retrieve webhook notification for payment event automation, manage multi-item order for Korean shopping cart automation, and integrate KakaoPay with Korean e-commerce, apps, and subscription services for end-to-end Korean digital wallet payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Korea digital wallet. FSC, PIPA. CID+admin_key. KR. Payment and financial data.
⚡ Reliability
Best When
A Korean e-commerce merchant, mobile app, or subscription service wanting AI agents to accept payments from KakaoPay's 37M+ Korean users through KakaoTalk-integrated one-tap checkout and subscription billing.
Avoid When
KAKAOTALK AUTHENTICATION IS REQUIRED: KakaoPay payment requires user to authenticate via KakaoTalk app; automated web-only checkout without KakaoTalk deep link creates broken authentication flow for mobile-first experience. ADMIN KEY SEPARATES FROM CID: KakaoPay authentication uses CID (partner key) + admin_key combination; automated single API key assumption creates authorization failure; automated must use both CID and admin_key in requests. REDIRECT IS REQUIRED FOR APPROVAL: KakaoPay payment requires redirecting user to KakaoPay approval page; automated direct payment without redirect creates incomplete payment; automated checkout must redirect web or invoke KakaoTalk app for approval. READY PAYMENT BINDING FOR SUBSCRIPTIONS: KakaoPay subscription (ready payment) requires prior SID binding; automated recurring charge without SID creates missing_subscription error; automated subscription must first complete SID binding flow.
Use Cases
- • Accepting one-tap payments from 37M Korean KakaoTalk users from Korean e-commerce checkout agents
- • Processing monthly subscription billing through KakaoPay for Korean SaaS platform agents
- • Integrating KakaoPay into mobile app checkout for Korean consumer service automation agents
- • Receiving webhook payment confirmations for Korean marketplace order fulfillment agents
Not For
- • Non-Korean markets (KakaoPay is Korea-only Korean Won platform)
- • International cross-border payments (KakaoPay is domestic KRW payments only)
- • Non-KakaoTalk users (KakaoPay requires KakaoTalk app for user authentication)
Interface
Authentication
KakaoPay uses CID (partner key) + admin_key for API authentication. REST API with form-encoded or JSON. Seoul, Korea HQ. Founded 2014 as Kakao Pay Corp. KOSPI: 377300. Kakao Corp subsidiary. Products: Easy pay, QR payment, subscription, investment, insurance, transfer. SDKs: None public. FSC-regulated. 37M+ users. Korea's dominant mobile payment platform integrated with KakaoTalk (50M+ users). Competes with Naver Pay and Toss for Korean mobile payments.
Pricing
Seoul KR. KOSPI:377300. Kakao Corp subsidiary. Transaction fee model. FSC regulated. KRW only.
Agent Metadata
Known Gotchas
- ⚠ DUAL KEY AUTHENTICATION (CID + ADMIN_KEY): KakaoPay requires both CID (partner identifier) and admin_key (secret) in all requests; automated single API key assumption creates authorization failure; automated must pass both keys correctly in headers
- ⚠ KAKAOTALK APP REQUIRED FOR USER AUTH: KakaoPay payment flow requires user to approve via KakaoTalk app; automated browser-only payment assumption creates broken flow for users without KakaoTalk; automated checkout must handle KakaoTalk app redirect or QR code fallback
- ⚠ READY PAYMENT SID REQUIRED FOR SUBSCRIPTIONS: KakaoPay subscription billing uses SID (subscription ID) from initial SID binding; automated recurring charge without prior SID binding creates subscription_not_found; automated recurring billing must complete SID binding on first payment
- ⚠ PAYMENT_READY AND PAYMENT_APPROVE ARE TWO STEPS: KakaoPay checkout requires payment/ready call then payment/approve after user completes KakaoTalk approval; automated single-call checkout assumption creates incomplete payment; automated must wait for user to approve in KakaoTalk before calling approve
- ⚠ DOCUMENTATION IS PRIMARILY IN KOREAN: KakaoPay developer documentation is predominantly Korean; automated integration without Korean language understanding creates documentation comprehension barrier; automated integration may need translation assistance
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for KakaoPay Korea Digital Wallet 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.