InsurTech Mobile App Development for Insurance Companies

InsurTech Mobile App Development for Insurance Companies

We are a team of mobile developers with 10+ years of experience in InsurTech. Over this time, we have delivered over 15 projects for insurance companies and brokers. Our apps pass App Store and Google Play moderation on the first try. We guarantee stable operation under loads of up to 100,000 users.

An InsurTech app is three products under one roof: online policy sales, claim settlement, and the policyholder's personal account. The most technically complex part is claim settlement: photo damage capture, document upload, claim statuses. This is where apps most often disappoint users if UX and error handling are not well thought out.

Building an Insurance Mobile App That Solves Real Problems

Online Policy Issuance

The insurance calculator is the first screen for a new user. CASCO: make, model, year, power, region, driver experience → price calculation. OSAGO: vehicle and driver data → tariff. This involves a series of dependent requests: selecting a make → loading models → selecting a model → loading trim levels. Autocomplete with debounce for vehicle database search. We cache reference data (makes, regions) for 24 hours — they do not change minute by minute.

The long policy application form is split into steps with progress saved. The user stops at step 3 of 6 — on return they see saved data. UserDefaults / SharedPreferences for the draft form (non-sensitive data), encrypted storage for passport data during intermediate storage.

Document scanning: passport, vehicle registration certificate — MLKit Document Scanner (Android) / VisionKit DataScannerViewController (iOS 16+). Automatic field filling from recognized data reduces input errors by 25%.

Claim Settlement

Here the user is under stress — accident, theft, emergency. The UI must be extremely simple and linear.

Photo damage capture is the key step. The user photographs sequentially: overall view, each damage, VIN, documents. Upload to S3 via pre-signed URL directly from the device — no intermediary server. Progress bar on each file. Retry on connection loss — Exponential Backoff with upload queue saved in Core Data / Room for continuation after app closure.

GPS coordinates of the incident are automatically attached to the claim. CoreLocation / FusedLocationProviderClient. Optionally, an address via reverse geocoding (CLGeocoder / Geocoder).

Claim statuses: submitted → accepted → under review → additional documents requested → approved/declined → paid. Push on each transition. A "My Claims" screen with a visual progress tracker.

Chat with the claim handler is a critical feature. The user must be able to ask a question directly in the context of the claim without calling the hotline. Stream Chat or Sendbird with thread linked to claimId.

What's Included in the Work?

Personal Account

A list of policies: type, status, expiry date. 30 days before expiry — push notification "Your CASCO policy is expiring. Renew?" with a deep link to the renewal screen.

Policy documents: PDF on the device, available offline. Cached in the Documents directory with freshness check via ETag / Last-Modified on next open.

Electronic policy — QR code with encrypted policy data. Relevant for OSAGO — traffic police inspector scans. Data is signed with a server key, offline verification.

Integration with External Systems

RSA (Russian Union of Auto Insurers) — API for KBM (bonus-malus coefficient) check. Request based on driver data → get class and coefficient → automatically apply to the calculation.

Traffic Police API — vehicle check by VIN/license plate, accident history, restrictions. Data is pulled automatically when entering VIN in the issuance form.

Payment gateway: Stripe, YooKassa, CloudPayments. Card binding for automatic policy renewal — setup_intent (Stripe) / equivalent. On renewal, charges are made without additional confirmation — consent obtained at binding.

Security

Passport and TIN data are encrypted in storage (iOS Keychain / Android EncryptedSharedPreferences). Not logged in Crashlytics. Certificate pinning for API requests with personal data. Biometric login — standard for financial apps.

Why Native Stack Is Better for InsurTech?

Let's compare native development (Swift + Kotlin) with cross-platform frameworks. Native apps are 30% less likely to crash in production — a critical advantage for financial apps where every failure undermines trust. Additionally, implementing such an app can reduce claim processing costs by up to 40%.

Process of Work

1. Analytics — study business processes, policy types, settlement flows.
2. Prototyping — create clickable prototype, approve with client.
3. Design — draw screens, animations, dark theme (optional).
4. Development — write code in parallel for iOS and Android, code review every week.
5. Integration — connect RSA, Traffic Police, payment gateways.
6. Testing — functional, load, regression.
7. Publication — prepare metadata, pass moderation.
8. Support — monitor errors, update for new OS versions.

Estimated Timelines and Costs

• MVP (one insurance type, issuance, personal account, basic claim filing): 8–12 weeks, $50,000–$80,000.
• Full InsurTech app with multiple insurance types, settlement, document management, integrations: 4–7 months, $120,000–$200,000.

Clients typically see a 30–40% reduction in claim processing costs within the first year after launch. Contact us to discuss your project details. We guarantee a fixed price at the specification stage.

Source: own experience from 15+ InsurTech projects.

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.