Glomo provides native SDKs for mobile platforms to help you embed payment checkout flows directly into your applications with minimal setup.
The React Native SDK enables you to embed Glomo payment checkout flows into your React Native application. It renders a secure WebView-based checkout and auto-detects the correct flow (LRS, standard, or subscriptions) based on your order.
- Supported Payment Flows: LRS, Standard (Cards, Bank Transfer, Pay via Bank), Subscriptions
- Platforms: iOS and Android
- Language: TypeScript / JavaScript
- Latest Version: v5.1.0 (Changelog)
The Flutter SDK provides a native widget (GlomoPayCheckout) for embedding Glomo checkout into Flutter applications. It supports multiple payment flows and handles device security compliance out of the box.
- Supported Payment Flows: LRS (Liberalised Remittance Scheme), Standard (Cards, Bank Transfer), Subscriptions
- Platforms: iOS and Android
- Language: Dart
- Latest Version: v2.2.0 (Changelog)
The Android SDK enables you to embed Glomo payment checkout flows into your native Android applications. It renders a secure WebView-based checkout and auto-detects the correct flow (LRS, Standard, or Subscriptions) based on your order.
- Supported Payment Flows: LRS, Standard (Cards, Bank Transfer), Subscriptions
- Platforms: Android (API 24+)
- Language: Kotlin
- Latest Version: v2.1.0 (Changelog)
The iOS SDK enables you to embed Glomo payment checkout flows into your native iOS applications. It presents a secure WebView-based checkout as a page sheet and auto-detects the correct flow (LRS, Standard, or Subscriptions) from your order.
- Supported Payment Flows: LRS, Standard (Cards, Bank Transfer), Subscriptions
- Platforms: iOS 16.0+
- Language: Swift
- Latest Version: v1.1.0 (Changelog)
The Unified SDK enables you to embed the Glomo checkout flow directly into your web application. It supports standard payments, LRS, subscriptions, and payment sessions with automatic flow detection.
- Supported Payment Flows: Standard, LRS, Subscriptions, Payment Sessions
- Platforms: Web (all modern browsers)
- Language: JavaScript / TypeScript
| Payment Flow | React Native SDK | Flutter SDK | Android SDK | iOS SDK | Unified SDK (Web) |
|---|---|---|---|---|---|
| LRS (Liberalised Remittance Scheme) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Standard Payments (Cards) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Standard Payments (Bank Transfer) | ✅ | ✅ | ✅ | ✅ | ✅ |
| Standard Payments (Pay via Bank) | ✅ | ❌ | ❌ | ❌ | ✅ |
| Subscriptions | ✅ | ✅ | ✅ | ✅ | ✅ |
| Payment Sessions | ❌ | ❌ | ❌ | ❌ | ✅ |
For Pay via Bank availability by market, see Pay via Bank.
Every Glomo SDK can ask the checkout page to present a light or a dark scheme, through a property called appColorScheme. It is a request, not an instruction, and dark mode is enabled per account.
The property is spelled the same everywhere, but its automatic value resolves to something different on each platform, and on the web SDK it is not even the default. Dark mode across the SDKs is the one place that states all five.
All Glomo SDKs follow the same integration pattern:
- Create an order on your backend using the Glomo API to obtain an
order_id. - Initialise the SDK in your app with your
publicKeyand theorder_id(orsubscriptionIdfor subscription payments). - Start the checkout by calling the SDK's
start()method — this launches the secure checkout UI. - Handle callbacks for
onPaymentSuccess,onPaymentFailure,onPaymentTerminate, andonSdkErrorto update your app state and backend accordingly.
All SDKs are built with the following security measures:
- WebView-based checkout — payment data is handled within a secure, isolated WebView and never passes through your application code.
- Signature verification — every payment success or failure callback includes a
signaturefield for backend verification. - Device compliance checks — the SDKs detect rooted (Android) or jailbroken (iOS) devices and block checkout initiation on non-compliant devices, in line with regulatory requirements.
- Mock mode isolation — using a
test_public key automatically enables mock mode, ensuring test transactions are completely isolated from live payments.
- If you are building a web application, use the Unified SDK (Web).
- If your app is built with React Native, use the React Native SDK. Supports LRS, standard payments, and subscriptions.
- If your app is built with Flutter, the Flutter SDK supports LRS, standard payments, and subscriptions.
- If you are building a native Android app (Kotlin/Java), use the Android SDK. Supports LRS, standard payments, and subscriptions.
- If you are building a native iOS app (Swift), use the iOS SDK. Supports LRS, standard payments, and subscriptions.