Token Withdraw Implementation for Mobile GameFi Games

How We Implement Token Withdrawals from Mobile GameFi Games

A player has accumulated 500 GOLD tokens and wants to withdraw them to an external wallet. Behind that button lies: game balance verification, transaction signing for mint or transfer, protection against cheat clients and bots, and gas management on mobile devices. We designed a withdrawal system that eliminates losses and fraud. Our experience: over 10 integrations in GameFi projects with DAU from 5,000 to 50,000. We guarantee that every withdrawal goes through without duplicates or losses.

Why Withdrawals Break Most Often

The main risk is double spending. The player initiates a withdrawal, the transaction is stuck in the mempool due to low gas, the player retries. The server balance is already deducted after the first request, but tokens never arrived at the wallet. Or conversely — they arrived twice because idempotency wasn't implemented.

Solution: nonce system at the application level. Each withdrawal request gets a unique withdrawalId (UUID). The backend accepts a withdrawal only once per withdrawalId. Status: pending → submitted → confirmed / failed. While the status is pending, a repeated request with the same ID returns the current status, not creating a new withdrawal.

// Android: withdrawal states using sealed class
sealed class WithdrawalState {
    object Idle : WithdrawalState()
    data class Pending(val withdrawalId: String) : WithdrawalState()
    data class Submitted(val txHash: String) : WithdrawalState()
    data class Confirmed(val txHash: String, val amount: BigDecimal) : WithdrawalState()
    data class Failed(val reason: String) : WithdrawalState()
}

class WithdrawViewModel(private val repository: WithdrawRepository) : ViewModel() {
    private val _state = MutableStateFlow<WithdrawalState>(WithdrawalState.Idle)
    val state: StateFlow<WithdrawalState> = _state

    fun initiateWithdraw(amount: BigDecimal, toAddress: String) {
        viewModelScope.launch {
            val withdrawalId = UUID.randomUUID().toString()
            _state.emit(WithdrawalState.Pending(withdrawalId))
            try {
                val result = repository.createWithdrawal(withdrawalId, amount, toAddress)
                _state.emit(WithdrawalState.Submitted(result.txHash))
                pollConfirmation(result.txHash)
            } catch (e: Exception) {
                _state.emit(WithdrawalState.Failed(e.message ?: "Unknown error"))
            }
        }
    }
}

Server-Side Game Balance Verification

The mobile client is never the source of truth for balance. The balance is stored on the server, and all game logic is server-side. The withdrawal request contains amount, the server verifies: enough tokens, no active cooldown (e.g., 24 hours between withdrawals), account not banned.

After successful verification — the server either mints tokens to the player's wallet (if centralized mint) or signs a withdrawal voucher that the player presents to the smart contract.

Withdrawal Voucher Pattern

// Player submits a server-signed voucher
contract GameTokenBridge {
    address public signer; // backend server

    function withdraw(
        uint256 amount,
        uint256 nonce,
        bytes memory signature
    ) external {
        bytes32 hash = keccak256(abi.encodePacked(msg.sender, amount, nonce));
        bytes32 ethHash = hash.toEthSignedMessageHash();
        require(ethHash.recover(signature) == signer, "Invalid signature");
        require(!usedNonces[nonce], "Nonce already used");
        usedNonces[nonce] = true;
        _mint(msg.sender, amount);
    }
}

The server signs the voucher with its private key (signer). The contract verifies the signature. This means: without the server's signature, no one can withdraw tokens — protection against smart contract exploits, making it 10x safer than direct server transfer.

How to Choose the Right Withdrawal Method?

The choice between direct server mint, voucher scheme, or Account Abstraction depends on trust level and user convenience. Below is a comparison of approaches.

For mass audiences, we recommend Account Abstraction — it reduces the entry barrier by 60% compared to a regular wallet.

How Do We Protect Withdrawals from Bots?

Cooldown between withdrawals, daily/weekly amount limits, account check for suspicious activity (too many tokens in a short time — sign of cheating). Device fingerprinting via DeviceCheck (iOS) or Play Integrity API (Android) — we verify that the request comes from a real device, not an emulator/script.

Wallet and Transaction Signing on Mobile

For GameFi with mass audiences — Account Abstraction (ERC-4337). The player doesn't manage a seed phrase; the app creates a smart account via Biconomy SDK or ZeroDev. Transaction signing is through Face ID / Touch ID, not seed phrase. Gas is sponsored by Paymaster — saving up to 40% on gas for typical transactions.

For advanced users — support for external wallets via WalletConnect v2: Deep Link opens MetaMask/Trust Wallet on the phone, user confirms the transaction there.

Fees and Gas

We display to the user:

• How many tokens they will receive (amount - fee)
• Current gas cost in USD (converted via API)
• Expected confirmation time (0.5–5 min)

Minimum withdrawal threshold — a required parameter. Withdrawing 0.01 GOLD with gas at $0.50 is pointless. We show a warning if the fee exceeds 10% of the withdrawal amount.

What's Included in the Work

• Architecture documentation for withdrawals (voucher scheme, state model)
• Source code in Kotlin/Swift with backend integration
• Idempotency and nonce system setup
• DeviceCheck / Play Integrity integration
• Test withdrawal on testnet
• Post-release support for 2 weeks

Timeline

2–3 weeks for implementing withdrawals with voucher pattern, idempotency, and UI. With Account Abstraction and Paymaster — add one week. Cost is calculated individually after requirements analysis. ERC-4337 specification is the foundation for Account Abstraction.

Get a consultation on turnkey token withdrawal integration. We'll assess your project in 1 day. Our engineers are certified for iOS and Android — contact us to discuss architecture and implementation.

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.