In-Game Item Marketplace Development for Mobile GameFi

In-Game Item Marketplace Implementation in Mobile GameFi

Developing an NFT marketplace inside a mobile game is one of the toughest challenges we face in GameFi projects. According to our data, up to 70% of users abandon marketplaces due to high gas fees and complex onboarding. Two worlds collide here: familiar mobile UX (fast, intuitive, no seed phrases) and blockchain reality (gas fees, transaction confirmation time, ownership via wallet). If this contradiction is not resolved, the marketplace simply won't be used. We guarantee a solution through experience integrating Account Abstraction and off-chain listings. If you are facing user drop-off or high gas costs, contact us — we will help.

Why Off-Chain Listings Are Critical for Mobile GameFi

A fully on-chain marketplace (like OpenSea v1) means every listing is a transaction. On mobile devices this is impractical: a user won't pay $0.50–5 in gas for each item listing. Off-chain listings work 10 times faster and save up to 90% on gas.

The right architecture for GameFi mobile is off-chain listings with on-chain settlements:

1. Seller signs the listing off-chain (signTypedData / EIP-712) — no transaction, no gas
2. Listing is stored in the application database
3. Buyer clicks "Buy" — only at this point does an on-chain transaction occur
4. Smart contract verifies the seller's signature, atomically transfers NFT to buyer and payment to seller

struct Listing {
    address seller;
    address nftContract;
    uint256 tokenId;
    address paymentToken;
    uint256 price;
    uint256 expiry;
    uint256 nonce;
}

bytes32 public constant LISTING_TYPEHASH = keccak256(
    "Listing(address seller,address nftContract,uint256 tokenId,address paymentToken,uint256 price,uint256 expiry,uint256 nonce)"
);

function buyItem(Listing calldata listing, bytes calldata signature) external {
    require(block.timestamp < listing.expiry, "Listing expired");
    require(!usedNonces[listing.seller][listing.nonce], "Nonce used");
    bytes32 digest = _hashTypedDataV4(keccak256(abi.encode(LISTING_TYPEHASH, listing)));
    require(ECDSA.recover(digest, signature) == listing.seller, "Invalid signature");
    usedNonces[listing.seller][listing.nonce] = true;
    IERC20(listing.paymentToken).transferFrom(msg.sender, listing.seller, listing.price);
    IERC721(listing.nftContract).safeTransferFrom(listing.seller, msg.sender, listing.tokenId);
}

This approach is used by Seaport (OpenSea v2) and Blur — proven design.

How to Provide a Seamless NFT Purchase UX on Mobile

The core problem: how does the user sign the purchase transaction without a seed phrase in the app? Consider three options:

For GameFi with a million-user audience, we recommend Account Abstraction. User logs in via Google/Apple — gets a smart account automatically. Paymaster sponsors gas, saving up to 90% on fees. Our team of certified engineers has experience implementing Privy and Dynamic in gaming projects.

What's Included in the Work

• Marketplace smart contract with audit
• Backend: metadata indexing, listings, full-text search
• Mobile client: item grid, detail card, purchase flow
• Wallet integration (WalletConnect or Account Abstraction)
• Filters, sorting, transaction history
• API and smart contract documentation
• Test documentation and launch support

How an Off-Chain Listing Works from the User's Perspective

The user enters the marketplace, selects an item, and clicks "Buy". The system verifies the listing signature that the seller created earlier off-chain. The blockchain transaction happens only at this moment — the user signs it via their smart account (biometrics). The entire process takes under 10 seconds, and gas is sponsored by the Paymaster.

Purchase Process: Step by Step

Each NFT item is a tokenId with metadata in tokenURI on IPFS or a centralized CDN. We index metadata into a database and serve it via REST API — the mobile client never accesses IPFS directly. Item images are delivered via CDN (CloudFront / Cloudflare), with client-side caching using Kingfisher (iOS) or Coil (Android). Lazy loading in lists — LazyColumn with AsyncImage in Compose, LazyVGrid in SwiftUI.

struct MarketplaceGridView: View {
    @StateObject var viewModel: MarketplaceViewModel

    let columns = [GridItem(.adaptive(minimum: 160), spacing: 12)]

    var body: some View {
        ScrollView {
            LazyVGrid(columns: columns, spacing: 12) {
                ForEach(viewModel.items) { item in
                    NFTItemCard(item: item)
                        .onAppear {
                            if item == viewModel.items.last {
                                viewModel.loadNextPage()
                            }
                        }
                }
            }
            .padding()
        }
    }
}

Filtering and Search

Filters: rarity (Rare/Epic/Legendary), item type (weapon/armor/pet), price range, payment asset. Sorting: by price, listing date, rarity. Full-text search by item name — via PostgreSQL tsvector or Elasticsearch on the backend. NFT attributes are indexed into a relational table at mint time — not parsed from IPFS JSON on each request.

Royalties and Moderation

With every P2P sale on the secondary market — automatic royalty deduction (2–5%) to the studio's wallet. ERC-2981 (NFT Royalty Standard) defines royaltyInfo(tokenId, salePrice) — the marketplace smart contract calls this before settlement and withholds the fee.

Reporting system for suspicious listings (cheat items, duplicates). Admin endpoint POST /listings/{id}/delist — removes the listing from the database. On-chain nothing changes (no transaction occurred), the item simply stops displaying. Stolen token blacklisting (if an account is compromised) — blacklist at the smart contract level: blockedTokens[tokenId] = true with a check in buyItem.

Timeline and Cost

Total: 8–10 weeks. Cost is calculated individually after requirements analysis. Get a consultation for your project right now — contact us for a free assessment.

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.