Turnkey Cashback Service Mobile App Development
A cashback service is the link between the user, the store, and the partner network. If attribution is broken, the business loses up to 30% of commissions. A typical mistake is using the built-in WebView for tracking. An incorrectly chosen transition mechanism leads to losing up to a third of partner commissions, directly impacting service profitability. That's why we pay special attention to choosing the component for opening links: on iOS it's SFSafariViewController, on Android — Chrome Custom Tabs. These components guarantee cookie transfer and correct cashback accrual, minimizing attribution losses. Over 5 years we have delivered 15+ projects and know all the pitfalls. We've helped dozens of clients launch their cashback services and save on lost commissions. Request a consultation for a detailed project estimate.
How Purchase Attribution Works in a Cashback App
Attribution is built on tracking links from partner networks: Admitad, CJ, Impact, or proprietary ones. Step by step:
- The app opens a tracking link:
https://trk.admitad.com/g/xxxxx?uid={userId} - The tracker redirects to the store, sets a cookie
- The user completes a purchase
- The store sends the conversion to the network with
uid - The network sends a postback to your server
- The server accrues cashback to the user with that
uid
The transition to the store uses SFSafariViewController (iOS) or Chrome Custom Tabs (Android). Never use the built-in WKWebView: its cookies are isolated and not shared with Safari, leading to up to 30% loss of attribution. Chrome Custom Tabs loads 20% faster than WKWebView and supports shared browser sessions — this increases conversion from clicks to purchases.
Comparison of store opening methods:
| Parameter | WKWebView | SFSafariViewController | Chrome Custom Tabs |
|---|---|---|---|
| Cookie isolation | Yes, isolated | No, shared with Safari | No, shared with Chrome |
| Attribution loss | Up to 30% | < 5% | < 5% |
| Load speed (relative) | 1x | 1.2x | 1.2x |
| Customizability | Full | Limited | Limited |
For iOS we use SFSafariViewController, for Android — Chrome Custom Tabs.
import SafariServices func openShopWithTracking(shop: Shop) { guard let trackingUrl = buildTrackingUrl(shop: shop, userId: currentUser.id) else { return } let safariVC = SFSafariViewController(url: trackingUrl) safariVC.preferredControlTintColor = .systemBlue present(safariVC, animated: true) // Record the transition locally for statistics analyticsService.track(.shopOpened(shopId: shop.id)) } // Android: Chrome Custom Tabs for tracking val customTabsIntent = CustomTabsIntent.Builder() .setShowTitle(true) .setColorScheme(CustomTabsIntent.COLOR_SCHEME_LIGHT) .build() customTabsIntent.launchUrl(this, trackingUri) Contact us for a project evaluation — we'll find the optimal tracking architecture.
Cashback Accrual and Payout
Cashback is stored as an internal user balance. Accrual statuses:
| Status | Description |
|---|---|
| PENDING | Transition recorded, purchase not confirmed |
| CONFIRMED | Store confirmed purchase (usually 30–90 days) |
| AVAILABLE | Ready for payout |
| WITHDRAWN | Paid out |
| CANCELLED | Purchase returned, cashback voided |
For payouts, we integrate YooKassa Payouts, Tinkoff Payouts API, or MTS Pay — each bank has its specifics. On average, payout implementation takes 1–2 weeks. We guarantee compliance with App Store Review Guidelines (Section 5.1) and Google Play policies.
More on push notification setup
Push notifications are a key channel for user retention. When cashback for a specific purchase is confirmed (CONFIRMED → AVAILABLE), we send a push with the amount. Also, when stores launch promotions, personalized offers based on history are sent. Stack: FCM (Firebase Cloud Messaging) for Android, APNs for iOS. Segmentation by interests, A/B testing of texts. Implementation takes about 1 week and includes deep link handling to return to the app.
Store Search and Filtering
The store list is the main screen. Filters: category, cashback size (fixed percentage or amount), newness, popularity. On the backend — full-text search via PostgreSQL tsvector or Elasticsearch. The client debounces requests:
// iOS: search with debounce using Combine @Published var searchQuery = "" init() { $searchQuery .debounce(for: .milliseconds(300), scheduler: RunLoop.main) .removeDuplicates() .filter { $0.count >= 2 } .sink { [weak self] query in self?.loadShops(query: query) } .store(in: &cancellables) } Why Trust Our Team with Development?
We have 5+ years of mobile development experience, 15+ published apps, and certifications from App Store and Google Play. We provide full documentation, source code, store access, and training for your team. A cashback service is a complex product with high accountability for attribution, so we use only proven trackers and strictly adhere to platform policies. Get a consultation on your project architecture.
What's Included in the Work (Deliverables)
- Architecture documentation (Tech Stack, Flow Charts)
- Source code for iOS (Swift 5.9+, SwiftUI/UIKit) and Android (Kotlin, Jetpack Compose)
- Access to App Store Connect and Google Play Console with configured certificates
- Integration with partner networks (Admitad, CJ, Impact) and payout providers
- Push notifications (FCM/APNs) with interest-based segmentation
- Team training (2 hours online) and user guide
Time Estimates
Basic version development (catalog, tracking, history) takes 4–6 weeks. Payout implementation takes another 1–2 weeks. Full cycle including backend integration — up to 10 weeks. The cost is calculated individually after analyzing your technical specification. We'll evaluate your project for free – contact us.