Choose Your Integration Path

Not sure which integration method is right for you? This guide will help you choose between plugins, SDKs, and direct API integration based on your needs.

Quick Decision Tree

What type of project are you building?

Integration Methods Comparison

1. E-Commerce Plugins (No Code)

Best for: Online stores using popular platforms

Pros:

• ✅ No coding required
• ✅ Quick setup (15-30 minutes)
• ✅ Tested and maintained
• ✅ Support for multiple payment methods
• ✅ Automatic updates

Cons:

• ❌ Limited customization
• ❌ Platform-specific
• ❌ May have feature limitations

Available Platforms:

• Shopify
• WooCommerce
• Magento
• PrestaShop
• OpenCart
• EC-CUBE
• Wix

👉 Start Here If: You're running an e-commerce store on one of these platforms and want the fastest setup.

2. Omise.js (Low Code)

Best for: Websites and web apps with minimal backend customization needs

Pros:

• ✅ Pre-built payment forms
• ✅ Handles tokenization automatically
• ✅ PCI compliance simplified
• ✅ Works with any backend
• ✅ Customizable styling

Cons:

• ❌ Less control over UI
• ❌ Still need backend integration
• ❌ JavaScript required

Integration Time: 2-4 hours

Code Example:

<!-- Include Omise.js -->
<script src="https://cdn.omise.co/omise.js"></script>

<!-- Payment form -->
<form id="checkout">
  <script type="text/javascript"
    src="https://cdn.omise.co/omise.js"
    data-key="pkey_test_YOUR_KEY"
    data-amount="100000"
    data-currency="thb"
    data-button-label="Pay Now">
  </script>
</form>

👉 Start Here If: You want a quick web integration with a payment form that "just works" and don't need heavy customization.

Get Started with Omise.js →

3. Mobile SDKs

Best for: Native mobile applications and cross-platform apps

Pros:

• ✅ Native UI components
• ✅ Platform best practices
• ✅ Handles tokenization
• ✅ Built-in error handling
• ✅ Optimized for mobile

Cons:

• ❌ Platform-specific (except Flutter)
• ❌ Still need backend integration
• ❌ App updates for SDK updates

Available SDKs:

• iOS: Swift/Objective-C
• Android: Java/Kotlin
• Flutter: Dart (cross-platform)
• React Native: JavaScript (cross-platform)

Integration Time: 1-2 days

👉 Start Here If: You're building a mobile app and want native payment UI components.

Browse Mobile SDKs →

4. Server Libraries + Custom Frontend

Best for: Custom applications with full control requirements

Pros:

• ✅ Full customization
• ✅ Complete control over UX
• ✅ Multiple language support
• ✅ All features available
• ✅ Direct API access

Cons:

• ❌ More development time
• ❌ More testing required
• ❌ Higher maintenance
• ❌ More PCI considerations

Available Libraries:

• Ruby, Python, PHP, Node.js
• Java, Go, .NET, Elixir

Integration Time: 1-3 days

👉 Start Here If: You need maximum flexibility and have development resources for custom implementation.

View Server Libraries →

5. REST API (Direct)

Best for: Custom integrations in any language

Pros:

• ✅ Works with any language
• ✅ Complete API access
• ✅ Maximum flexibility
• ✅ No library dependencies

Cons:

• ❌ Most development effort
• ❌ Manual error handling
• ❌ Need to implement everything
• ❌ More maintenance

Integration Time: 2-5 days

👉 Start Here If: You're using a language without an official library or need extremely custom integration.

6. Payment Links (No Code)

Best for: Simple sales, invoices, social media commerce

Pros:

• ✅ Zero coding required
• ✅ Instant setup
• ✅ Shareable via any channel
• ✅ Hosted checkout page
• ✅ Mobile-friendly

Cons:

• ❌ No customization
• ❌ External checkout experience
• ❌ Limited automation
• ❌ Manual process

Setup Time: 5 minutes

👉 Start Here If: You need to accept payments immediately without building anything.

Create Payment Links →

Feature Comparison Matrix

Payment Method	Setup Time	Coding Required	Customization	Maintenance	All Payment Methods	Mobile Ready	Difficulty
E-Commerce Plugins	15-30 min	❌	Low	Low	✅	✅	Easy
Omise.js	2-4 hours	✅	Medium	Low	✅	✅	Medium
Mobile SDKs	1-2 days	✅	High	Medium	✅	✅	Medium
Server Libraries	1-3 days	✅	High	Medium	✅	❌	Hard
REST API	2-5 days	✅	Full	High	✅	❌	Hard
Payment Links	5 min	❌	None	None	✅	✅	Easy

By Use Case

Subscription/Recurring Billing

Recommended: Server Libraries + Omise.js

Why: You need to store customer payment methods and charge them repeatedly. This requires backend logic.

Features Needed:

• Customer management
• Card storage
• Scheduled charges
• Webhook handling

Learn about Recurring Payments →

One-Time Purchases

Recommended: Omise.js or E-Commerce Plugin

Why: Simple checkout flow without complex requirements.

Features Needed:

• Token creation
• Charge creation
• Basic error handling

Quickstart Guide →

Marketplace/Platform

Recommended: Full API Integration

Why: Need to manage multiple merchants, split payments, handle complex flows.

Features Needed:

• Sub-merchant management
• Transfer splitting
• Advanced reporting
• Chain keys

Contact Sales for marketplace solutions.

Mobile Commerce

Recommended: Mobile SDKs

Why: Native mobile experience with optimized UI components.

Features Needed:

• Tokenization in app
• Native payment forms
• Biometric authentication
• Deep linking

Mobile Integration Guide →

International Sales

Recommended: Full API Integration

Why: Need to handle multiple currencies, regions, and payment methods.

Features Needed:

• Multi-currency support
• Regional payment methods
• Currency conversion
• Localization

Multi-Currency Guide →

Technical Considerations

PCI Compliance

Method	PCI Burden	Reason
Plugins	Minimal	Plugin handles card data
Omise.js	Minimal	Omise.js tokenizes before your server
Mobile SDKs	Minimal	SDK tokenizes before your server
Server Libraries	Low	Still use tokenization
REST API	Medium	Need to implement securely

tip

All methods keep card data out of your servers if implemented correctly. Always use tokenization!

Hosting Requirements

Method	Requirements
Plugins	Platform hosting (managed)
Omise.js	Web hosting with HTTPS
Mobile SDKs	App store deployment
Server Libraries	Server with HTTPS
REST API	Server with HTTPS
Payment Links	No hosting needed

Development Skills Needed

E-Commerce Plugins:

• Platform administration
• Basic configuration

Omise.js:

• HTML/JavaScript
• Basic backend development
• HTTPS/SSL knowledge

Mobile SDKs:

• Swift/Kotlin/Dart
• Mobile development experience
• Backend API development

Server Libraries:

• Backend programming
• API integration
• Database management
• Security best practices

REST API:

• HTTP/REST APIs
• JSON handling
• Authentication
• Error handling
• Security hardening

Migration Paths

Starting Simple, Scaling Later

You can start with one method and migrate later:

1. Start: Payment Links (immediate sales)
2. Upgrade: Plugin (e-commerce launch)
3. Scale: Custom API (advanced features)

No Lock-In

All methods use the same Omise backend. You can switch or combine approaches without data migration.

Combining Approaches

You can use multiple methods simultaneously:

• Web: Omise.js integration
• Mobile: Native SDKs
• Admin: Payment Links for manual sales
• Backend: Server libraries for automation

Next Steps Based on Your Choice

Chose E-Commerce Plugin?

1. Find your platform in Plugins
2. Follow installation guide
3. Configure payment methods
4. Test with test mode
5. Go live

Chose Omise.js?

1. Read Omise.js Guide
2. Include the script on your page
3. Implement token handling
4. Build backend charge endpoint
5. Test and deploy

Chose Mobile SDK?

1. Select SDK: iOS, Android, or Flutter
2. Install via package manager
3. Implement payment UI
4. Build backend API
5. Test on devices

Chose Server Library?

1. Pick your language in Server Libraries
2. Install library
3. Build frontend tokenization
4. Implement backend logic
5. Set up webhooks

Chose REST API?

1. Review API Documentation
2. Implement authentication
3. Build tokenization flow
4. Create charge endpoint
5. Handle errors and edge cases

Chose Payment Links?

1. Log into Dashboard
2. Create payment link
3. Share via email/social media
4. Track payments in dashboard

FAQ

Can I switch integration methods later?

Yes! All methods use the same Omise backend and APIs. You can:

• Start with a plugin and move to custom integration later
• Use plugins for web and SDKs for mobile simultaneously
• Migrate between approaches without losing data

Your charges, customers, and transactions remain in your Omise account regardless of integration method.

Which method is most secure?

All methods are secure when implemented correctly. The key is to:

• Always use tokenization (all methods do this)
• Never store card data on your servers
• Use HTTPS for all connections
• Keep secret keys on your server only

Plugins and Omise.js have slightly less implementation risk because card data handling is built-in.

Which method gives me the most payment methods?

All methods support all of Omise's 40+ payment methods. The difference is in how easily you can add them:

• Plugins: Usually have checkboxes to enable methods
• Omise.js: Supports all methods with minimal code changes
• SDKs: Support all methods with native UI
• API: Requires code for each new method

Do I need separate integrations for web and mobile?

Generally yes, but they share the backend:

• Frontend: Different (Omise.js for web, SDKs for mobile)
• Backend: Same server code can handle both
• Dashboard: Single view of all transactions

You can reuse your charge-creating backend logic across platforms.

Can I use multiple integration methods at once?

Absolutely! Common scenarios:

• Plugin for main store + Payment Links for offline sales
• Omise.js for web + Mobile SDKs for apps
• Custom API for web + Plugin for legacy system

All transactions appear in your dashboard regardless of how they were created.

What if my platform/language isn't supported?

Use the REST API directly! It works with any language that can:

• Make HTTP requests
• Parse JSON
• Handle HTTPS

You can also build a thin wrapper around the API for your specific needs.

Still Not Sure?

Try this:

1. Start with Payment Links (5 minutes) to make your first sale
2. Explore the Quickstart to understand the basics
3. Contact us if you need help choosing: support@omise.co

Or start testing immediately with our Quickstart Guide!

---

Ready to build? Choose your path above and start integrating!