Omise Southeast Asia Payment Gateway API
Omise (now Opn Payments) Southeast Asia payment gateway REST API for merchants in Thailand, Japan, Singapore, and Malaysia to accept credit cards, PromptPay QR, TrueMoney Wallet, internet banking, and local SEA payment methods with tokenization and marketplace payments. Enables AI agents to manage payment charge creation and capture for SEA e-commerce automation, handle PromptPay QR for Thailand real-time payment automation, access TrueMoney Wallet for Thailand digital wallet automation, retrieve token-based card storage for secure recurring payment automation, manage refund and dispute processing for order management automation, handle multi-currency charge for international customer billing automation, access marketplace transfer for platform payment splitting automation, retrieve transaction reporting for financial reconciliation automation, manage webhook notification for real-time payment event automation, and integrate Omise with e-commerce platforms and SEA business systems for end-to-end Southeast Asia payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
SEA payments. PCI-DSS. API key. TH/JP. Payment and transaction data.
⚡ Reliability
Best When
A merchant selling in Thailand, Japan, or Singapore wanting AI agents to automate PromptPay, TrueMoney Wallet, and local SEA payment method acceptance through Omise/Opn Payments' developer-friendly SEA payment gateway.
Avoid When
COUNTRY-SPECIFIC PAYMENT METHODS REQUIRE ACTIVATION: Omise payment methods (PromptPay, TrueMoney, Rabbit LINE Pay) require per-country merchant activation; automated SEA payment checkout must display only activated payment methods; automated display of all SEA payment methods without activation check creates unavailable payment option. THAILAND VS JAPAN PLATFORM DIFFERENCES: Omise Thailand and Omise Japan operate with some regional differences in supported payment methods and API behaviors; automated multi-country SEA deployment must test country-specific payment flows; automated assumption of uniform payment behavior across Thailand and Japan creates country-specific checkout errors. PROMPTPAY PAYMENT CONFIRMATION TIMING: PromptPay payments require customer action in their banking app; automated checkout must implement payment confirmation polling (webhook or status API); automated order fulfillment before PromptPay confirmation creates orders without confirmed payment.
Use Cases
- • Accepting PromptPay and TrueMoney in Thailand from SEA payment agents
- • Processing international cards in SEA from cross-border e-commerce agents
- • Tokenizing customer cards from recurring billing agents
- • Splitting marketplace payments from Thailand platform agents
Not For
- • Indonesia-centric payments (use Midtrans or Xendit for Indonesia focus)
- • Global payment orchestration (use Adyen or Stripe for multi-region enterprise)
- • Africa and LATAM payments (use Flutterwave or Mercado Pago for other emerging markets)
Interface
Authentication
Omise (Opn Payments) uses Secret Key and Public Key for authentication (Basic Auth Base64). REST API with JSON. Bangkok, Thailand and Tokyo, Japan dual HQ. Founded 2013 by Jun Hasegawa and Ezra Don Harinsut. Backed by Ascend, SMBC, East Ventures ($18M+ raised). Rebranded to Opn Payments in 2022. Products: Credit cards, PromptPay, TrueMoney, internet banking, marketplace payments. SDKs: Ruby, PHP, Python, Java, JavaScript, Go. PCI DSS. Serves merchants in Thailand, Japan, Singapore. Competes with 2C2P, Xendit, and Stripe for SEA payments.
Pricing
Bangkok TH. VC-backed. No monthly fee. Per-transaction fees vary by payment method and country.
Agent Metadata
Known Gotchas
- ⚠ SECRET KEY vs PUBLIC KEY CONTEXT: Omise Secret key for server-side charge creation and Public key for client-side card tokenization; automated server-side public key usage creates unauthorized charge error; automated client-side secret key exposure creates security vulnerability
- ⚠ CHARGE vs SOURCE vs TOKEN OBJECT TYPES: Omise charges can be created from Token (card), Source (alternative payment — PromptPay, wallets), or Customer (stored card); automated payment routing must use correct object type for payment method; automated Token charge for PromptPay creates payment method type mismatch error
- ⚠ PROMPTPAY SOURCE CREATION BEFORE CHARGE: PromptPay payments require two-step flow — create Source object (returns QR code/URL) then create Charge from Source; automated PromptPay checkout must implement two-step flow; automated single-step charge attempt for PromptPay creates source type not found error
- ⚠ MARKETPLACE TRANSFER REQUIRES RECIPIENT CREATION: Omise marketplace transfers require Recipient object creation with Thai bank account; automated marketplace payout requires per-vendor Recipient creation with bank details; automated marketplace payout without Recipient object creates unregistered recipient error
- ⚠ WEBHOOK CHARGE STATUS vs FINAL SETTLEMENT STATUS: Omise charge webhook fires on status change but final settlement may take T+1 to T+3 days; automated settlement reconciliation must distinguish charge completion from settlement; automated same-day settlement assumption for all payment methods creates premature reconciliation
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Omise Southeast Asia Payment Gateway 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.