Files
2nd/10_Wiki/Topics/Domain_Programming/Coding/Android_BillingClient_IAP.md
T
Antigravity Agent c24165b8bc refactor(topics): 멀티 에이전트용 지식 재편 — _Common(공통 기본기) + Domain_* 구조
에이전트 8종(대화형/프로그래머 C·S/디자이너/설계자/기획자/QA/PD/PM)에게
[공통 기본 능력 + 롤별 Specialty] 2층으로 지식을 주입하기 위한 재분류.
문서 내용·포맷은 무수정, 폴더 이동만 (6,372개 문서 수 보존 확인).

- Topic_Programming → Domain_Programming (내부 구조 보존)
- Topic_Graphic → Domain_Design
- Topic_Business → Domain_Product
- Topic_General → Domain_General
- _Common 신설: Math(구 Topic_Math_Specialty), Reasoning(구 General/From_Thinking & Reasoning),
  Reasoning_Creativity(구 General/From_창의성), Communication(Poetic_Blog_Writing + From_writing)
- 타 도메인의 From_* 폴더는 유지 (출처 표기일 뿐, 이미 도메인에 맞게 분류된 문서)
- 빈 폴더 정리 (memory/procedures)
- 에이전트→폴더 매핑은 workspace의 .astra/agent-knowledge-map.json (9개 에이전트)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-11 11:05:56 +09:00

5.1 KiB

id, title, category, status, source_trust_level, verification_status, created_at, updated_at, tags, tech_stack, applied_in, aliases
id title category status source_trust_level verification_status created_at updated_at tags tech_stack applied_in aliases
android-billingclient-iap Android Billing Client — IAP / Subscription Coding draft B conceptual 2026-05-09 2026-05-09
android
billing
iap
subscription
vibe-coding
language applicable_to
Kotlin / com.android.billingclient
Android
Google Play Billing
Purchase
acknowledgePurchase
server-side validation

Android Billing Client (IAP)

Google Play 결제. acknowledge / consume 안 하면 사용자 환불. 서버 검증 (Real-Time Developer Notifications + Subscription API) 필수.

📖 핵심 개념

  • ProductDetails: Google Play Console 등록 상품.
  • Purchase: 구매 결과. acknowledged / consumed 상태.
  • Acknowledge: 3일 안 안 하면 자동 환불.
  • Server: Pub/Sub RTDN 으로 갱신 / 환불 / 만료 통지.

💻 코드 패턴

의존성

implementation("com.android.billingclient:billing-ktx:7.0.0")

Setup

class BillingManager(ctx: Context) : PurchasesUpdatedListener {

    private val client = BillingClient.newBuilder(ctx)
        .setListener(this)
        .enablePendingPurchases()
        .build()

    suspend fun startConnection(): BillingResult = suspendCancellableCoroutine { cont ->
        client.startConnection(object : BillingClientStateListener {
            override fun onBillingSetupFinished(result: BillingResult) { cont.resume(result) }
            override fun onBillingServiceDisconnected() { /* retry later */ }
        })
    }

    suspend fun queryProducts(ids: List<String>): List<ProductDetails> {
        val params = QueryProductDetailsParams.newBuilder()
            .setProductList(ids.map {
                QueryProductDetailsParams.Product.newBuilder()
                    .setProductId(it)
                    .setProductType(BillingClient.ProductType.SUBS)
                    .build()
            })
            .build()
        return client.queryProductDetails(params).productDetailsList ?: emptyList()
    }

    fun launchPurchase(activity: Activity, product: ProductDetails) {
        val flow = BillingFlowParams.newBuilder()
            .setProductDetailsParamsList(listOf(
                BillingFlowParams.ProductDetailsParams.newBuilder()
                    .setProductDetails(product)
                    .setOfferToken(product.subscriptionOfferDetails!!.first().offerToken)
                    .build()
            ))
            .setObfuscatedAccountId(currentUserId) // server matching
            .build()
        client.launchBillingFlow(activity, flow)
    }

    override fun onPurchasesUpdated(result: BillingResult, purchases: List<Purchase>?) {
        if (result.responseCode == BillingClient.BillingResponseCode.OK && purchases != null) {
            for (p in purchases) handlePurchase(p)
        }
    }

    private fun handlePurchase(purchase: Purchase) {
        if (purchase.purchaseState != Purchase.PurchaseState.PURCHASED) return

        // 1) 서버 검증
        scope.launch {
            val verified = api.verify(purchase.purchaseToken, purchase.products.first(), currentUserId)
            if (!verified) return@launch

            // 2) acknowledge (subscription) or consume (consumable)
            if (!purchase.isAcknowledged) {
                val params = AcknowledgePurchaseParams.newBuilder()
                    .setPurchaseToken(purchase.purchaseToken)
                    .build()
                client.acknowledgePurchase(params) {}
            }
        }
    }
}

서버 검증 (Subscription API)

// Backend
import { google } from 'googleapis';

const auth = new google.auth.GoogleAuth({ keyFile: serviceAccountPath, scopes: ['https://www.googleapis.com/auth/androidpublisher'] });
const pub = google.androidpublisher({ version: 'v3', auth });

const r = await pub.purchases.subscriptionsv2.get({
  packageName: 'com.example.app',
  token: purchaseToken,
});

if (r.data.subscriptionState === 'SUBSCRIPTION_STATE_ACTIVE') {
  await grantEntitlement(userId, productId);
}

RTDN (Real-Time Developer Notifications)

  • Google Cloud Pub/Sub 구독.
  • 갱신 / 환불 / 만료 / 환경 변경 notify.
  • 서버가 사용자 entitlement 갱신.

🤔 의사결정 기준

상품 type
1회 영구 (광고 제거) INAPP
사용 후 소진 (코인) INAPP + consume
월/년 구독 SUBS + offer
무료 trial SUBS + introductoryPrice offer

안티패턴

  • acknowledge 안 함: 3일 후 자동 환불.
  • client-side validation 만: 우회 가능. 서버 + signature 검증.
  • consume vs acknowledge 헷갈림: consumable 만 consume, 그 외 acknowledge.
  • obfuscatedAccountId 미설정: 결제 ↔ 사용자 매핑 어려움.
  • RTDN 없음: 환불 / 만료 모름.
  • client 가 entitlement 결정: 서버가 진실. 클라는 표시.
  • 동시에 여러 구독 가능: 의도와 다른 구독 활성. SkuDetails 하나만 active.

🤖 LLM 활용 힌트

  • BillingClient 7+ + obfuscatedAccountId + 서버 검증 + RTDN 4종 세트.
  • acknowledge / consume 분리.

🔗 관련 문서