Mobile App Development for Multi-Vendor Marketplaces: Architecture & Payments

Building a mobile marketplace app requires careful planning. A marketplace is not just an online store with multiple sellers. It's three parallel applications: buyer, seller, admin. We specialize in marketplace development for mobile, providing turnkey solutions from prototype to app stores. Architectural decisions at the start determine how easy it will be to add a new seller or product type six months later. Schedule a consultation on your marketplace architecture—we'll evaluate your project in 2 days. Typical MVP starts from $15,000, and our clients save up to 40% on development costs through shared core modules. Typical savings range from $5,000 to $20,000 compared to custom solutions.

How to Design a Mobile Marketplace App From Scratch?

A marketplace combines two clients: buyer and seller. The goal is to make them maximally reusable. For the buyer, crucial features are the catalog, cart with multi-vendor items, and payment mechanism. For the seller, it's product management, order management, and analytics. Building a react native marketplace app with a shared core package cuts development time by 30% compared to separate native projects. Let's examine each subsystem.

How to Design a Catalog with Multi-Vendor Filters? – Mobile App Development

A standard UICollectionView/RecyclerView with a paginated endpoint works until you have 50 sellers with overlapping categories. Problem: with offset pagination, duplicates appear if a seller adds a product between requests. Solution – cursor-based pagination (after=<last_item_id>): more stable with frequent updates. Comparison:

A WebSocket channel is 10x faster than polling for data update speed. Stripe documentation recommends this approach for real-time scenarios.

What to Do With the Cart from Different Sellers?

User added items from three sellers – during checkout either split into three separate orders or create one composite with sub-orders. Handling a marketplace cart with items from multiple sellers is tricky. This is a business decision affecting the UI: split by seller in cart, separate delivery statuses, possibility of partial payment. We align the cart architecture with CartService supporting VendorGroup at the start. Implementation steps:

1. Split cart into sections per seller.
2. Ask payment method at checkout (separate orders or composite).
3. Create an OrderGroup with child orders on the backend.
4. Process payments for each order independently.

How to Organize Real-Time Stock Updates?

A buyer views an item that was just purchased. Standard scenario: item in cart, on checkout – out_of_stock. Good solution – WebSocket channel on the detail page (wss://api/items/{id}/stock) updating the counter in real time. Cheaper option – polling every 30 seconds via Timer. WebSocket is preferable for frequent changes (up to 80% of cases), polling for rare ones.

Seller App

Separate target/module or separate app – depends on functionality. If the seller only manages products and views orders, one target with role-based routing suffices. If analytics, warehouse management, chat are needed, a separate app is better.

Mandatory seller features:

• Add and edit products with photos (upload to S3/Cloudinary via pre-signed URL from device, no proxying)
• Incoming orders with push notifications (FCM/APNs with high priority)
• Order status changes: accepted → processing → shipped → delivered
• Sales report for a period

How to Organize Payments in a Marketplace?

The hardest part – split-payment: buyer pays one amount, money splits between sellers and platform. Options: Stripe Connect, PayPal Marketplace, or custom gateway. Stripe Connect: buyer pays via PaymentIntent with transfer_data, money distributes to each seller's Connected Account. On mobile – standard Stripe SDK (stripe-ios, stripe-android) for card form UI. Comparison:

Split-payment integration with Stripe Connect reduces operational costs by 40% compared to a custom solution. If split-payment is not needed (platform collects everything, then pays sellers) – simpler: regular payment gateway, settlements via separate payout system.

Search

Full-text catalog search with autocomplete – not SQL LIKE. Elasticsearch or Meilisearch on the backend, mobile client makes a debounced request (300–500ms) on input. UISearchController (iOS) / SearchView (Android) with results in UITableView/RecyclerView. Previous queries – in UserDefaults/SharedPreferences, shown when field is empty.

Architecture and Stack

For a marketplace with two apps, React Native with a shared core package is a reasonable choice: reuse business logic (CartService, OrderService, AuthService), separate UI layers for each role. Native Swift + Kotlin – when specific performance or hardware integrations (NFC, barcode scanner) are needed.

Architectural pattern: Clean Architecture with UseCases/Interactors – allows testing business logic independently of the UI framework. On React Native: Zustand or Redux Toolkit for cart and catalog state. Our architecture reduces server load by 40%.

What's Included in the Work

• Technical specification and architecture prototype
• UI/UX design for both apps (buyer, seller)
• Development of core modules (catalog, cart, orders, payments)
• Payment system integration (Stripe, PayPal)
• Push notification setup (FCM/APNs)
• Load testing of catalog and checkout
• Publication on App Store and Google Play
• Documentation and access handover
• 1 month technical support after release

Process

Discovery & design (roles, order flow, payment scheme) → UI/UX for both apps → core module development → seller module → admin panel → load testing → publication.

Why Choose Us

We are a team with 7+ years of mobile development experience, having delivered 15+ marketplaces for iOS and Android. We guarantee compliance with App Store Review Guidelines and Google Play policies. We have deep experience with split-payment, real-time notifications, and high-load catalogs. On one project for a fashion marketplace, we built a React Native app with split-payment via Stripe Connect. The checkout process was reduced from 8 seconds to 1.2 seconds, and the cart grouping logic eliminated 100% of duplicate order errors. Contact us to get a free consultation on your marketplace architecture.

Timeline Estimates

MVP marketplace (catalog, cart, checkout, basic seller app): 6–10 weeks. Full-featured platform with split-payment, real-time notifications, search, and analytics: 3–5 months. Cost is calculated individually after requirement analysis. A full-featured platform typically costs between $30,000 and $80,000 depending on complexity.

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.