LINE Pay Asia Payment API
LINE Pay Asia payment REST API for merchants to accept LINE wallet payments, QR codes, and in-app checkout from LINE's messaging super app ecosystem across Japan, Taiwan, Thailand, and Indonesia with 195M+ LINE users for e-commerce, in-app, and physical merchant payment integration. Enables AI agents to manage LINE Pay payment request for Asia messaging wallet checkout automation, handle QR code generation for in-store LINE Pay merchant payment automation, access LINE Pay online checkout for e-commerce payment automation, retrieve payment confirmation and status for transaction automation, manage refund and cancellation for order management automation, handle payment notification for webhook event automation, access transaction reporting for Asia payment analytics automation, retrieve merchant settlement for payment reconciliation automation, manage recurring payment authorization for subscription automation, and integrate LINE Pay with Japanese and Taiwanese e-commerce, food delivery, and retail platforms for end-to-end LINE ecosystem payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Asia e-wallet. FSA. HMAC-SHA256. JP/TW. Mobile payment data.
⚡ Reliability
Best When
A Japan or Taiwan merchant or LINE mini-app developer wanting AI agents to automate LINE Pay wallet payment acceptance, QR code generation, and payment confirmation for the LINE super app ecosystem.
Avoid When
CHANNEL ID AND SECRET PAIR MARKET-SPECIFIC: LINE Pay uses Channel ID + Channel Secret that are market-specific (Japan, Taiwan, Thailand); automated multi-market integration must maintain separate credentials per market; automated single-credential multi-market use creates authentication failure in non-registered markets. HMAC-SHA256 SIGNATURE WITH NONCE: LINE Pay request authentication uses HMAC-SHA256 on Channel Secret + request path + body + nonce; automated request must compute signature with correct nonce; automated wrong signature scheme creates authentication failure. CONFIRM API REQUIRED AFTER CHECKOUT: LINE Pay uses two-step checkout (reserve → confirm); automated payment flow must call confirm API after customer completes LINE Pay checkout; automated payment completion without confirm API creates payment reserved but not captured. LINE MINI-APP PAYMENT USES JS SDK NOT REST: LINE mini-app payments use LINE SDK not direct REST API; automated LINE mini-app payment must use LINE Frontend Framework (LIFF) SDK; automated REST API call in LINE mini-app creates incompatible flow.
Use Cases
- • Accepting LINE Pay wallet payments from Japan/Taiwan e-commerce checkout agents
- • Processing in-app payments within LINE mini-apps from Asia mobile payment agents
- • Generating QR codes for in-store LINE Pay from merchant POS automation agents
- • Confirming LINE Pay transactions from order fulfillment agents
Not For
- • Non-LINE markets (LINE Pay available in Japan, Taiwan, Thailand, Indonesia only)
- • China payments (LINE is not available in mainland China)
- • Credit card processing (LINE Pay is wallet-based; use KOMOJU for Japan card)
Interface
Authentication
LINE Pay uses Channel ID + Channel Secret with HMAC-SHA256 signing for authentication. REST API with JSON. Tokyo, Japan and Taipei, Taiwan. LINE Corporation (NAVER/SoftBank JV). 195M+ LINE users. Products: QR payment, online checkout, subscription, mini-app payments. SDKs: Node.js, PHP, Python, Java, .NET, Ruby, Go. FSA registered (JP). PCI DSS. Multi-market Asia payment.
Pricing
Tokyo JP / Taipei TW. LINE Corp (NAVER/SoftBank). Per-transaction fee varies by market. Merchant registration per market.
Agent Metadata
Known Gotchas
- ⚠ TWO-STEP RESERVE-CONFIRM FLOW: LINE Pay checkout requires reserve (create payment request) then confirm (capture after customer pays); automated checkout must call confirmPayment after customer returns; automated reserve-only creates payment incomplete forever
- ⚠ NONCE MUST BE ALPHANUMERIC MAX 20 CHARS: LINE Pay HMAC nonce must be alphanumeric and max 20 characters; automated nonce generation must use alphanumeric characters only; automated UUID-with-hyphens nonce creates invalid nonce format rejection
- ⚠ JAPANESE YEN NO DECIMAL FOR JAPAN: LINE Pay Japan amounts are in integer yen; automated Japan payment must use integer amount; automated decimal yen creates invalid amount error; Taiwan amounts use TWD with cents
- ⚠ CALLBACK AND CANCEL URL REQUIRED: LINE Pay reserve requires explicit confirmUrl and cancelUrl; automated payment must provide both URL parameters; automated payment without cancelUrl creates missing required parameter error
- ⚠ MULTI-LANGUAGE DOCUMENTATION: LINE Pay documentation available in Japanese and English; Japanese documentation may have more detail; automated integration relying solely on English docs may miss Japan-specific API behavior
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for LINE Pay Asia Payment 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.