Mobile SDKs
Integrate Pine Labs Mobile SDKs for Android and iOS to deliver secure, app-native checkout flows with backend verification and webhook-backed reliability.
Pine Labs Mobile SDKs help you build native in-app payment journeys while keeping order creation, trust checks, and final status reconciliation on your backend.
When To Use Mobile SDKs
Use Mobile SDKs when your payment flow is inside:
- Android applications
- iOS applications
- App-first commerce journeys
- In-app repeat checkout scenarios
Choose Your Platform
Android
Native Android SDK with built-in UPI app detection, intent handling, and payment lifecycle callbacks.
iOS
Native iOS SDK with UPI scheme support, secure payment flow, and UIKit/SwiftUI compatibility.
Flutter
Cross-platform Flutter SDK with native Android and iOS payment support through a unified Dart API.
Mobile Integration Model
| Component | What it handles |
|---|---|
| Android/iOS SDK | Native checkout interaction and payment UI flow |
| Merchant backend | Order creation, signature validation, and fulfillment control |
| Webhooks | Event-driven payment state updates and retry-safe reconciliation |
Prerequisites
- Pine Labs merchant onboarding complete.
- API credentials stored securely in backend systems.
- Platform app setup (Android/iOS release configuration).
- Backend endpoints for order creation and payment verification.
- Test matrix for app lifecycle interruptions and network failures.
Recommended Mobile Checkout Flow
- App calls backend to create order.
- Backend returns order context to the app.
- App launches Mobile SDK checkout.
- Customer completes payment in app flow.
- Backend confirms final status from webhook events.
- App reflects final status after trusted backend confirmation.
Mobile-Specific Best Practices
| Area | Recommendation |
|---|---|
| App resilience | Handle app background/foreground transitions during payment flow |
| Network robustness | Implement retry-safe status polling only as fallback to webhook flow |
| Security | Never embed secrets in app binaries |
| UX | Show clear pending, success, and failed payment states |
| Observability | Log correlation IDs for order, payment, and webhook events |
Next Steps
- Read Web SDKs Overview for browser-based checkout integrations.
- Refer to Webhooks for final state handling.
- Use Error Codes to design robust retry and user messaging.