Automated Crypto Payment Conversion to Fiat for Merchants

Streamlining Crypto Payments into Fiat for Your Merchant App

A merchant accepted payment in USDT, and the next day the rate dropped 4% — the money just sits on the wallet. Automatic conversion to fiat immediately after transaction confirmation is not a "nice to have" but a business requirement, especially with high volumes. We implement this scenario in the mobile app, synchronizing on-chain events with conversion through a processor or exchange without losing transactions during failures. The approach is tailored to the merchant's model: for small business, a ready-made processor is sufficient; for large volumes, direct exchange integration yields 10–20 times lower fees.

How Automatic Crypto-to-Fiat Conversion Works

Two main approaches exist: through payment processing (Coinbase Commerce, NOWPayments, CryptoCloud) and through direct exchange integration (Binance API, Bybit API). Each has its own logic on the mobile client.

Through Payment Processing

NOWPayments and similar processors accept crypto and automatically convert to fiat before withdrawal. The mobile client sends a POST /v1/payment with the parameter payout_currency: "USD" — the processor takes on the exchange rate risk. The app only needs to:

1. Request a payment address and amount
2. Show a QR code or Deep Link (bitcoin:addr?amount=0.001)
3. Poll status via GET /v1/payment/{id} every 15 seconds or use WebSocket
4. Display status: waiting → confirming → confirmed → finished

The problem with polling: when the Bitcoin network is congested, confirming may hang for 40+ minutes. The user will close the app. A push notification via FCM/APNs is needed when the status changes — the backend receives a webhook from the processor and sends push notifications. Our experience shows that without push, up to 30% of users lose the transaction during confirmation.

Through Binance API

Direct integration: after receiving crypto on a custodial wallet, we make POST /sapi/v1/convert/getQuote — get a quote, then POST /sapi/v1/convert/acceptQuote. The quote is valid for 10 seconds. If expired — retry. On the mobile client, this process is hidden behind the backend; the client only sees the final fiat balance.

// Example of conversion status display (SwiftUI)
struct ConversionStatusView: View {
    @StateObject var viewModel: ConversionViewModel

    var body: some View {
        switch viewModel.status {
        case .waitingPayment(let address, let amount):
            QRCodeView(address: address, amount: amount)
        case .confirming(let confirmations, let required):
            ConfirmationProgressView(current: confirmations, required: required)
        case .converting:
            LoadingView(text: "Converting to USD...")
        case .completed(let fiatAmount):
            SuccessView(amount: fiatAmount)
        case .failed(let error):
            ErrorView(error: error)
        }
    }
}

Dealing with Rates and Slippage

The user sees "you'll get $99.50" — but actually receives $97.80 due to slippage during conversion. It is necessary to explicitly show estimated_rate and locked_rate (if the processor supports rate locking for 15–20 minutes). CryptoCloud supports rate locking; NOWPayments does not. To display live rates in the app, we use WebSocket from Binance wss://stream.binance.com:9443/ws/btcusdt@ticker or CoinGecko REST with 30-second caching. This approach gives the user transparency and reduces support inquiries.

How to Ensure Security on the Mobile Client

Private wallet keys — never on the mobile device. The mobile client communicates only with its own backend. Exchange API keys — only on the server, protected via Vault or environment variables. On iOS we use Keychain for storing session tokens, on Android — EncryptedSharedPreferences from Jetpack Security (official documentation). Our 5+ years of experience in crypto integrations guarantee certified security practices.

What's Included in the Work

• Business requirements audit and approach selection (processing or exchange) considering volumes and geography
• Server-side conversion layer design: backend service, webhooks, retries on failures
• Mobile client development: payment screens, status screens, push notifications
• Integration with chosen processor or exchange (testing in Testnet/Sandbox)
• Documentation and merchant team training
• Post-release support: monitoring, alerts, bug fixing

Stages and Timeline

Total: 3–5 days for integration via ready-made processing, 2–3 weeks for direct exchange integration. Typical cost: $2,000–$5,000 for processing, $10,000–$25,000 for direct exchange. With 50+ successful projects completed, we deliver reliable solutions. Contact us for a free estimate.

Why Automate Conversion?

Manual conversion means lost time and exchange rate risk. Our experience shows that automation reduces costs by 15–20% thanks to rate locking and eliminating human error. You get transparency of every conversion step in real time. To calculate cost and timeline for your project, contact us.

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.