POS Terminal Integration for Mobile Apps: Full Cycle

How to Connect a POS Terminal to a Mobile App?

Connecting a mobile app to a POS terminal is not just "send the amount to the terminal". It's integration with proprietary hardware protocols—each manufacturer has their own—plus handling all possible communication failures during a financial transaction. Our company has 7+ years of experience in mobile development and has implemented over 20 integrations with POS terminals for various acquirers. Our approach covers all edge cases to ensure every transaction completes correctly.

Typical scenario: a cashier in a supermarket processes a payment via a mobile app, the terminal authorizes the card, but the connection drops. What to do? Our solution includes an automatic status request for the last transaction and a reconnection mechanism with 5 attempts, achieving a 99% success rate in determining the status. Order a turnkey integration—we handle all stages: from protocol analysis to testing on real hardware. We'll evaluate your project within two business days.

Protocols and Manufacturers

Most POS terminals in retail communicate via one of the standard interface protocols:

• ECR protocol (Electronic Cash Register) — a set of commands to send the amount from the cash register app to the terminal. Each bank-acquirer or manufacturer has its own implementation: Sberbank (SBOL), VTB, Ingenico, Verifone—all differ in command syntax and response fields.
• OPI (Open Payment Initiative) / OPOS (OLE for POS) — more standardized protocols, popular in Europe.
• Proprietary SDKs: PAX A-series, Sunmi V2, Newland—have their own Android SDKs (the terminal itself runs Android, we call AIDL interfaces or Intents).

Before starting development, we clarify with the client: which specific terminal, which bank-acquirer, which protocol is supported. This is not a developer's technical choice—it's a fact about the installed equipment.

What Interfaces Are Used?

Bluetooth (BLE + Classic). The terminal acts as a GATT server (BLE) or classic Bluetooth serial device. On iOS: CoreBluetooth for BLE; classic Bluetooth only through the ExternalAccessory framework with MFi certification. This is an important limitation: most POS terminals use the classic Bluetooth SPP profile, and without MFi certification from the terminal manufacturer, iOS cannot connect via classic BT. Android has no restrictions—BluetoothSocket + RFCOMM.

USB. Android: UsbManager, UsbDeviceConnection. iOS: Lightning/USB-C accessory—again requires MFi. In practice, USB connections are rarer than Bluetooth.

TCP/IP (Wi-Fi / LAN). The terminal is on the local network; the app connects via IP:Port and sends commands in text or binary format. URLSession / OkHttp for HTTP commands or CFStream / Java Socket for raw TCP. The most predictable interface from iOS's perspective.

Payment Flow

1. The app forms a "sale" command with the amount and additional parameters.
2. Sends it to the terminal.
3. The terminal shows the payment screen to the user and accepts the card.
4. Returns a response: status (approved/declined/error), authorization code, RRN, masked PAN.
5. The app processes the response and continues the business flow (closes the receipt, updates the order).

Steps 2–4 may take up to 60–90 seconds with slow payment processing. During this time, we show a spinner with the message "Waiting for terminal response" and a "Cancel" button (which sends a cancel command to the terminal, not just closes the screen).

What to Do When Connection Drops During a Transaction?

The most unpleasant case: the transaction was sent to the terminal, connection was lost—the app doesn't know whether the payment went through. The terminal authorized the card, but the response didn't arrive.

The correct approach: upon connection loss—attempt to get the status of the last transaction ("last operation request" command). If the terminal responds, we take the status from there. If not, we show the operator "Status unknown, check the terminal" and save the transaction in PENDING status. Automatic charge when status is unknown is unacceptable.

Reconnect logic: on Bluetooth disconnection—automatic reconnection with 5 attempts, exponential backoff. Connection status is always visible in the UI (status icon).

Void and Refund

Void (reversal) — before the financial day closes. Refund — after. Both require separate commands to the terminal with the RRN of the original transaction. We implement both scenarios so the operator can correct errors.

Platform Comparison: Android vs iOS

If the client requires iOS and the terminal only works with classic Bluetooth without MFi, the only path is TCP/IP through an intermediate adapter or switching to a terminal with BLE/TCP support.

By the way, the BLE protocol typically provides lower latency (up to 50 ms) compared to classic Bluetooth (100–200 ms), speeding up the transaction by 2–4 times. This is important for high-throughput scenarios. More details in Apple's CoreBluetooth documentation.

Common Integration Mistakes

• Not accounting for MFi certification on iOS for classic Bluetooth—results in connection impossibility.
• Lack of retry logic on disconnection—lost transactions.
• Using the wrong protocol (e.g., ECR for a terminal that only supports OPI).
• Incorrect parsing of the terminal response (different error codes from different manufacturers).

What's Included in the Work

• Analysis of equipment and acquirer protocols.
• Implementation of the transport layer (Bluetooth/USB/TCP).
• Development of command protocol (sale, void, refund, status request).
• Handling edge cases (connection drop, timeout, unknown status).
• Testing on a real terminal in the acquirer's test mode.
• Integration documentation for client support.
• Warranty on the transport layer: 6 months free support.

The integration cost is fixed at the specification stage, and the return on investment is achieved through automation of manual data entry. Get a consultation for your project—we'll assess the complexity and timeline.

Process

Determine terminal model and protocol → study acquirer documentation → implement transport layer (BT/USB/TCP) → command protocol (sale, void, refund, status request) → handle edge cases (connection drop, timeout) → test on real terminal in acquirer test mode → production testing → deployment.

Timeline Estimates

Basic integration (sale + response) over a single protocol with one interface: 3–5 days. Full set of operations (sale, void, refund, status request) with retry/reconnect logic and multiple interfaces: 2–3 weeks.

Our team consists of mobile developers with 7+ years of experience in iOS (Swift, SwiftUI, CoreBluetooth) and Android (Kotlin, Jetpack Compose, BluetoothSocket). We have worked with terminals from PAX, Ingenico, Verifone, Sunmi. We guarantee integration quality and transparency at every stage.

Order a POS terminal integration—and we'll ensure stable operation of the payment module in your app.

Payments in Mobile Apps: In-App Purchase, StoreKit 2, Google Billing, Stripe, RevenueCat

In every monetization project, we balance App Store and Google Play policies, PCI DSS requirements, and purchase verification logic on the backend. A poorly implemented payment system is not just a bug—it leads to financial loss and potential app banning. Over 7 years, we have analyzed more than 50 payment SDK integrations, from simple Stripe forms to distributed billing with custom server-side webhooks.

In-App Purchase: Two Platforms, Two Different APIs

If your app sells digital content or subscriptions, Apple and Google require you to use their payment systems. This is non-negotiable: violating App Store rule 3.1.1 or Google Play Developer Policy results in app removal. Physical goods and offline services are a different story.

StoreKit 2 (iOS 15+)

StoreKit 2 is a complete overhaul of the original StoreKit with async/await API. Product.products(for:), product.purchase(), Transaction.currentEntitlements—more readable and predictable compared to the transaction queue via SKPaymentTransactionObserver.

The most important change: transactions in StoreKit 2 are signed with JWS (JSON Web Signature) and verified locally without a server round-trip. Transaction.verificationResult returns .verified(Transaction) or .unverified(Transaction, VerificationError). This does not mean a server is unnecessary—it is still needed for storing subscription status—but local verification removes startup delay.

StoreKit.AppTransaction verifies the actual app download from the App Store. Required for paid downloads or non-renewing purchases.

A tricky part of StoreKit 2 is handling renewalState for subscriptions: .subscribed, .expired, .inBillingRetryPeriod, .inGracePeriod, .revoked. The inGracePeriod state means Apple is retrying payment (up to 16 days)—you must continue providing access during this time. Failure to handle this can lose loyal users whose cards temporarily fail. Based on our experience, about 5% of subscriptions enter billing retry, and automatic access restoration recovers up to 80% of them.

Google Play Billing Library (v6+)

Google Billing is more complex than StoreKit in terms of scenario handling. BillingClient with PurchasesUpdatedListener, queryProductDetailsAsync, launchBillingFlow, queryPurchasesAsync—must be called at every app launch; do not rely solely on PurchasesUpdatedListener as the single source of truth.

Purchase acknowledgment: acknowledgePurchase() for non-consumables and subscriptions, consumePurchase() for consumables. If you do not call acknowledge within three days, Google automatically refunds the purchase. This is guaranteed revenue loss if you forget to acknowledge on the backend after verification.

ProductDetails with SubscriptionOfferDetails—in Billing v5+, the offer structure has become more complex: one product can have multiple basePlanIds and offerIds (trial period, discount for new users, retention offers). BillingFlowParams.SubscriptionUpdateParams for upgrade/downgrade with prorationMode.

Why Is Server-Side Verification Mandatory?

Never trust only client-side code when unlocking paid content. Client-side verification can be bypassed by modifying the app.

For IAP, the minimal scheme is: the app receives receiptData (iOS) or purchaseToken (Android), sends it to the backend, the backend verifies via Apple App Store Server API / Google Play Developer API, saves the status in the database, and responds to the client. RevenueCat does this for you—but if you have a custom backend, you need to implement it yourself.

Webhooks are more important than they seem. Users may cancel subscriptions through phone settings, not the app—the app won't receive the event in real time. Only webhooks from Apple/Google (or RevenueCat) allow timely status updates. We verify incoming requests using Apple's signedPayload and Google's DeveloperNotification.

How Does RevenueCat Simplify Integration?

Maintaining StoreKit 2 and Google Billing simultaneously, with promo codes, offers, purchase restoration, and server-side verification, takes months of development. RevenueCat handles most of this layer.

RevenueCat is not just a payment SDK. It offers:

• A unified API for iOS and Android (and Stripe for web)
• Server-side verification and subscription status storage
• Webhooks for events (purchase, renewal, cancellation, billing issue)
• Analytics for cohorts, MRR, churn
• A/B testing of offers via Experiments

Purchases.configure(withAPIKey:) at startup, Purchases.shared.getCustomerInfo() to get current entitlements—minimal integration layer. Purchases.shared.purchase(package:) instead of directly calling StoreKit/Billing.

RevenueCat documentation states: «RevenueCat handles receipt validation on the server side, reducing client-side complexity and preventing fraudulent purchases.»

Limitations of RevenueCat: it is paid (free up to $2.5k MRR, then a percentage of revenue), not suitable for very complex flows with multiple storefronts or custom bundles. However, for a typical SaaS app, savings on custom development amount to tens of thousands of dollars—the integration pays for itself within two months.

Stripe in Mobile Apps

Stripe is used for physical goods, services, and B2B payments where IAP is not required by platform policy.

Stripe iOS SDK and Android SDK—PaymentSheet for ready-made payment UI, PaymentSheetFlowController for custom UI with saved cards. Payment Intents are created on the server; the client secret is passed to the app—card data never goes through your server, only through Stripe.

Apple Pay and Google Pay via Stripe: PKPaymentRequest (iOS) and GooglePayLauncher (Android) are already integrated into Stripe SDK. Apple Pay conversion rates are 1.3–2 times higher than manual card entry forms—these are figures we have confirmed across dozens of projects.

Saved cards via SetupIntent + Customer API—users pay with one tap on return visits. Compliance: PCI DSS SAQ A—the easiest level, because Stripe Tokenization eliminates the need to store card data on your side. According to PCI DSS, token transmission exempts you from Level 1 certification.

3DS2 (Strong Customer Authentication) is mandatory for payments in the EU under PSD2. Stripe handles it automatically via PaymentIntent.confirmPayment, but you need to correctly handle the .requiresAction status and return the user to the appropriate screen after authentication.

What Is Included in the Work (Deliverables)

Process and Timeline

We start by clarifying the business model: subscriptions, one-time purchases, consumables, freemium. The architecture depends on this. Testing IAP requires Sandbox accounts (Apple) and License Testers (Google)—this is a separate environment setup.

Apple's Sandbox behaves differently from production: subscriptions renew every 5 minutes instead of monthly, inGracePeriod works differently. It is essential to test scenarios: trial expiration, cancellation, billing retry, refund.

The cost is calculated individually based on the set of tools and complexity of server-side logic. On average, we fit within a budget for a typical integration, but the savings from preventing errors and churn offset this investment within a few months.

Get a consultation for your project—contact us. We will help you choose the optimal payment architecture that passes store reviews and does not break under peak loads.