Mobile App Development for P2P Cryptocurrency Exchange

Note: when a client comes to us with an idea for a P2P cryptocurrency exchange, the first thing we discuss is the escrow mechanism. Without it, trades between peers turn into "trust or lose." We bake escrow into the architecture from the start: either a smart contract on an EVM-compatible chain or a custodial service with multisig. For a successful P2P crypto exchange mobile app development, we recommend integrating smart contract escrow, KYC, WalletConnect, and trader chat. This combination ensures security, compliance, and user convenience. The choice depends on speed, fee, and decentralization requirements. With proper implementation, the average gas fee on Ethereum is around $5 per trade, while on Polygon it's $0.02 — that's 250 times cheaper. Over 10,000 trades, using Polygon saves $49,800. Let's dive into the details.

P2P crypto exchange development considerations

How to Build a P2P Crypto Exchange Architecture

Smart Contract Escrow

The seller deposits crypto into the contract via approve() + deposit(). The buyer transfers fiat by any means, clicks "confirm receipt," the contract calls release() and sends the crypto to the buyer. If there is a dispute, an arbitration address can call resolveDispute(winner).

// Simplified escrow logic on an EVM-compatible chain
contract P2PEscrow {
    enum Status { ACTIVE, RELEASED, REFUNDED, DISPUTED }

    struct Trade {
        address seller;
        address buyer;
        address token;
        uint256 amount;
        Status status;
    }

    mapping(uint256 => Trade) public trades;
    address public arbiter;

    function deposit(uint256 tradeId, address buyer, address token, uint256 amount) external {
        IERC20(token).transferFrom(msg.sender, address(this), amount);
        trades[tradeId] = Trade(msg.sender, buyer, token, amount, Status.ACTIVE);
    }

    function release(uint256 tradeId) external {
        Trade storage t = trades[tradeId];
        require(msg.sender == t.seller, "Only seller");
        require(t.status == Status.ACTIVE);
        t.status = Status.RELEASED;
        IERC20(t.token).transfer(t.buyer, t.amount);
    }

    function dispute(uint256 tradeId) external {
        Trade storage t = trades[tradeId];
        require(msg.sender == t.buyer || msg.sender == t.seller);
        t.status = Status.DISPUTED;
    }

    function resolveDispute(uint256 tradeId, address winner) external {
        require(msg.sender == arbiter);
        Trade storage t = trades[tradeId];
        require(t.status == Status.DISPUTED);
        IERC20(t.token).transfer(winner, t.amount);
    }
}

Smart Contract Escrow vs Custodial Wallet: Which is Better for Your P2P Exchange?

Both approaches have trade-offs. Smart contracts are fully decentralized and users retain control of funds, but incur gas fees and slower confirmation. Custodial wallets offer instant transactions and no gas, but require trust in the operator. For high-volume mobile apps with many small trades, custodial may be better for user experience. For a truly decentralized exchange, smart contracts are the way to go.

Custodial Escrow

The server holds crypto in a hot wallet. Faster, no gas, simpler UX. Requires high security standards: HSM for private keys, multisig wallets (Gnosis Safe), cold/hot wallet separation.

Mobile Client: Architecture and Web3

On iOS we use web3.swift or custom integration via URLSession to JSON-RPC. On Android — web3j. For the user's wallet — WalletConnect v2 (Sign SDK): allows connecting MetaMask, Trust Wallet, Rainbow and sending transactions via deep link without storing keys in the app. According to the official WalletConnect documentation, connection takes less than 2 seconds.

// WalletConnect v2 connection on iOS
import WalletConnectSign

class WalletService {
    func connect() async throws {
        let methods: Set<String> = ["eth_sendTransaction", "personal_sign"]
        let chains = [Blockchain("eip155:1")!] // Ethereum mainnet
        let namespaces: [String: ProposalNamespace] = [
            "eip155": ProposalNamespace(
                chains: chains,
                methods: methods,
                events: ["chainChanged", "accountsChanged"]
            )
        ]
        let uri = try await Sign.instance.connect(requiredNamespaces: namespaces)
        // Open Deep Link to wallet or show QR
        await UIApplication.shared.open(uri.deepLink)
    }
}

How to Integrate WalletConnect: Step-by-Step Guide

1. Install the SDK: pod 'WalletConnectSwiftV2' for iOS or implementation 'com.walletconnect:sign:2.0' for Android.
2. Set up the project in the WalletConnect cloud dashboard and get a projectId.
3. Initialize the client via Sign.instance.configure(projectId: ...).
4. Call connect(requiredNamespaces:) to create a pairing.
5. Display the URI as a QR code or deep link.
6. Handle sessionSettlement and sessionProposal events.

Order Book and Real-Time Updates

The list of buy/sell orders must update in real time — WebSocket from the server. New order, price change, trade closure — all pushed via ws://. On the client, URLSessionWebSocketTask (iOS) or OkHttp WebSocket (Android).

Order filtering: currency, payment method (Tinkoff, Sberbank, SBP, cash), amount range, seller rating. A rating system is a mandatory P2P feature. Without it, the platform won't gain trust. We store trade history and reviews; rating is computed on the server.

Why KYC and Trader Chat Are Mandatory?

User Verification (KYC)

Regulatory requirements for P2P platforms: at least basic KYC (passport photo + selfie). On iOS — VisionKit document scanner, on Android — ML Kit Document Scanner. We offload document verification to SumSub, Veriff, or Jumio via their mobile SDKs — implementing liveness detection ourselves doesn't make sense.

Default limits for unverified users are determined per project, raised after KYC.

Trader Chat

An inbuilt chat between buyer and seller within a trade is critical. Without it, disputes cannot be resolved. We implement it using Firebase Realtime Database or Stream Chat SDK — the latter provides ready-made UI for iOS/Android, saving 2–3 days of development (2x faster than building from scratch). Messages are encrypted end-to-end via libsignal if additional privacy is needed.

Fiat payment confirmation — a bank screenshot uploaded in the chat. Stored in Firebase Storage or S3 with presigned URLs.

What's Included in Development

Security

Rate limiting on order creation endpoints — without it, competitors could flood the market with junk orders. Anti-scam checks: new accounts cannot immediately publish large orders. 2FA via TOTP (Google Authenticator) is mandatory for withdrawals. Biometric authentication via LocalAuthentication (iOS) / BiometricPrompt (Android) to confirm trades.

Work Stages

Total: 8–12 weeks depending on escrow type and feature set. Cost is calculated individually after requirement analysis. Typical development budget for a full-featured P2P exchange mobile app is between $50,000 and $100,000, depending on complexity.

Estimated savings: $49,800 on gas for 10,000 trades when using Polygon vs Ethereum. Contact us for a project evaluation and get a free consultation. Our company has 5+ years of experience in blockchain development, with over 50 successful crypto projects and a team of 30+ engineers. We guarantee timeline adherence and transparent code without hidden surprises. Get a detailed cost and timeline estimate in response to your inquiry. Also order a preliminary assessment — we will prepare a proposal within 24 hours.

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.