Integrations
Topics covered on this page
Omise provides plugins, libraries, and SDKs for all major programming languages and platforms. These plugins, libraries, and SDKs help integrate merchant systems with Omise's servers.
Each platform name in the following tables links to its own dedicated setup guide, with the installation steps and code examples specific to that platform — this page is for finding the right one and checking what it supports, not for implementation details.
Payment methods marked (Deprecated) are being phased out and should not be used for new integrations. Availability of the remaining methods depends on your country and your account's own supported payment methods, not just the plugin or library itself — see payment methods by country for a breakdown, and confirm current availability for your account before committing to an integration.
Choosing your integration path
- Already using a supported e-commerce platform (EC-CUBE, Magento, OpenCart, PrestaShop, Shopify, or WooCommerce)? Use its plugin — it's the fastest path and requires no custom code.
- Building a custom checkout and need to collect card details in the browser? Use a client-side library (Omise.js works for any platform) to tokenize the card, then a server-side library to process the resulting token.
- Already have a token and just need to process payments from your backend? Use a server-side library for your language directly.
- Want to know what's available in your country? See payment methods by country.
- Platform not listed anywhere in the following tables? See the FAQ for what to do.
All integration options
Every plugin, client-side library, and server-side library in one place. The Type column shows which category each option belongs to, color-coded for quick scanning — blue for plugins, green for client-side, amber for server-side — see the following sections for what each type actually means and how to use it.
Payment methods by country
Looking for what's available in one of Omise's operating markets rather than by platform? This table breaks the same payment methods down by country instead. Some methods, like ShopeePay and GrabPay, are available in more than one country.
| Country | Payment Methods |
|---|---|
| Thailand | Bill Payment (Deprecated), Bangkok Bank (Bualuang mBanking), KBank (K PLUS), Krung Thai (KTB NEXT), Krungsri (KMA), SCB (SCB Easy), PromptPay, Rabbit Line pay, TrueMoney Wallet, WeChat Pay (Barcode), Installments, Alipay CN, Alipay HK, Kakao Pay, ShopeePay, Credit and Debit Cards, Google Pay |
| Singapore | OCBC Digital, PayNow, ShopeePay, GrabPay, DANA, GCash, Kakao Pay, Alipay CN, Alipay HK, Credit and Debit Cards, Google Pay |
| Malaysia | Boost, DuitNow Online Banking/Wallets, DuitNow QR, FPX, GrabPay, Maybank QR, Touch 'n Go, ShopeePay, Credit and Debit Cards, Google Pay |
| Japan | Konbini, Pay-easy, and Online Banking, PayPay, Credit and Debit Cards, Google Pay |
Plugins
Plugins act as a bridge between merchant platforms such as Magento and Omise's servers.
Client-side libraries
Omise's client-side libraries securely accept and tokenize sensitive data directly on the user's device. These libraries use public key authentication.
Omise Dart is a special case: unlike the other libraries listed here, it supports both client-side tokenization and server-side processing, so it appears twice in the preceding table — once as a client-side option and once as a server-side option.
Server-side libraries
Omise provides server-side libraries to process already tokenized data. These libraries run on the merchant system and use secret key authentication.
Contributing
Omise's open-source libraries are available on GitHub.
If you would like to contribute by adding features or fixing issues or bugs, send a pull request.
FAQ
What's the difference between a client-side library and a server-side library? Client-side libraries run on the customer's own device and use public key authentication to securely accept and tokenize sensitive data, such as card details. Server-side libraries run on your systems and use secret-key authentication to process already tokenized data, such as creating a charge from a token. Omise Dart is an exception — it supports both.
Do I need both a client-side library and a server-side library? Typically, yes, for card payments — a client-side library (or Omise.js) tokenizes the card on the customer's device, and a server-side library then uses that token to create a charge or perform other actions on your server.
Which e-commerce platforms have a dedicated plugin? EC-CUBE, Magento, OpenCart, PrestaShop, Shopify, and WooCommerce each have a dedicated plugin.
Is a plugin required, or can I integrate directly with a library instead? A plugin is the fastest path if you're already using one of the supported e-commerce platforms. If you're building a custom integration, or your platform doesn't have a dedicated plugin, use the client-side and server-side libraries directly instead.
What if my e-commerce platform or programming language isn't listed? Use the client-side and server-side libraries directly rather than a plugin — most languages have a dedicated server-side library, and Omise.js works as a general-purpose client-side option regardless of platform. If your specific language isn't covered by any library either, you can call the Omise API directly over HTTP.
How do I contribute to an Omise library? Omise's libraries are open source on GitHub. To contribute a feature or fix a bug, send a pull request.
