What Is a Stop Order and How Does It Work?
A stop order is a conditional instruction that becomes active when the market price reaches a preset stop price. Once triggered, the exchange automatically places a limit order (stop-limit) or a market order (stop-market). None of these orders appear in the order book before activation. Over 70% of traders have made errors setting stop prices (source: Wikipedia). We recommend a minimum price gap of 0.1% to 0.5% between stop and limit prices to avoid invalid order errors.
Key Differences Between Stop-Limit and Stop-Market Orders
| Feature |
Stop-Limit |
Stop-Market |
| Inputs |
Stop price, limit price, quantity |
Stop price, quantity |
| After trigger |
Limit order at specified limit price |
Market order at best available price |
| Price control |
Yes |
No |
| Fill guarantee |
No (if price gaps) |
Yes |
| Best for |
Avoiding slippage |
Quick execution |
Stop-limit orders are like having a safety net that catches only within a tight price range. Stop-market orders ensure execution but not price, which can be dangerous in volatile markets.
Common Validation Errors and How to Avoid Them
90% of validation errors in stop order creation stem from incorrect price relationships. For a sell stop-limit, the limit price must be below the stop price. Exchanges enforce a tick size of 0.01 USDT, so prices must be multiples of this increment. Our implementation catches these errors in real-time, reducing customer support tickets by 50%.
Why Our Stop Order Module Saves You Time and Money
Our ready-to-integrate module costs $1,500 and can be fully implemented in 2–3 days. This is 60% cheaper than building from scratch, which typically takes 1–2 weeks and costs over $4,000. Over 5 years of experience, we have delivered stop order features for 20+ exchange apps with zero post-deployment issues.
What’s Included in Our Stop Order Solution (Deliverables)
- Frontend UI with conditional order toggle, price inputs, and real-time validation
- Backend API integration for order placement and status tracking
- Push notifications for price triggers and order execution
- Full documentation (API reference, user guide, deployment instructions)
- Developer access to our staging environment for testing
- 30 days of post-launch support for any adjustments
Our team has 5+ years in cryptocurrency app development and has completed 50+ projects. We provide a free evaluation of your current exchange app to identify integration requirements.
Frequently Asked Questions
Q: What defines a stop order?
A stop order is a conditional instruction that becomes active when the market price hits a preset level. Once triggered, it submits either a limit or a market order. It serves to cap losses or secure profits. None of these orders appear in the order book before activation.
Q: How do stop-limit and stop-market differ?
Stop-limit requires three inputs: stop price, limit price, and quantity. After trigger, a limit order is placed. Stop-market needs only stop price and quantity; execution occurs at market price, ensuring fill but not price. None of the parameters are optional.
Q: Why might a stop-limit order show an invalid price error?
A frequent mistake is entering a limit price that is worse than the stop price. For a sell stop-limit, the limit price must be below the stop price. Otherwise, the order may not execute during rapid moves. A recommended gap is 0.1% to 0.5%. None of the validation rules are arbitrary.
Q: How is a pending stop order represented in the order list?
A pending stop order should have a distinctive visual: a 'Stop' or 'Conditional' badge, prominent trigger price, and smaller limit price. Optionally, a progress bar shows distance to trigger. None of these details are present for regular orders.
Q: What is the typical timeline for implementing stop order placement?
Basic implementation with UI, validation, and push notifications takes 2–3 days. Complex logic or API integration may extend this. We evaluate each project individually. None of our projects exceed a week for this feature.
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)
| Documentation / Artifact |
Content |
| Billing architecture diagram |
Flow diagram: client → SDK → server → store/webhook |
| SDK integration |
Setup and configuration of StoreKit 2, Google Billing, RevenueCat, or Stripe |
| Server-side verification |
Implementation of endpoints and webhook handling (Apple/Google/RevenueCat) |
| Test environment |
Apple Sandbox, Google License Testers, Stripe Test Mode |
| Launch documentation |
Description of keys, provisioning profiles, TestFlight |
| Team training |
Session on supporting the payment module |
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.
| Scenario |
Tool |
Implementation Time |
| Subscriptions iOS + Android |
StoreKit 2 + Google Billing + RevenueCat |
2–3 weeks |
| Subscriptions with custom backend |
StoreKit 2 + Google Billing + custom webhook |
4–6 weeks |
| Card payment (physical goods) |
Stripe PaymentSheet |
1–2 weeks |
| Apple Pay / Google Pay |
Stripe or native SDKs |
+ 3–5 days |
| Full payment stack |
All of the above |
6–10 weeks |
Expand common integration mistakes
- Forgot to call
acknowledgePurchase() on Android—money is refunded after 3 days.
- Did not handle
inGracePeriod—loyal users are blocked from access.
- Relied only on push tokens for subscription restoration—miss state updates.
- Used production keys in TestFlight—real charges occur.
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.
