docs: clarify that transactionReceipt is now purchaseToken

Author: hyochan

docs/blog/2025-09-13-v3.0.0.md

@@ -32,6 +32,11 @@ import AdFitTopFixed from "@site/src/uis/AdFitTopFixed";
 
 ## 💥 Breaking Changes
 
+- Removed fields
+
+  - Removed `transactionReceipt` (use `purchaseToken` on all platforms). On iOS, `purchaseToken` contains the JWS representation previously accessed via receipts.
+  - Removed `jwsRepresentationIOS` in favor of the unified `purchaseToken`.
+
 - Removed functions
 
   - `getProducts`, `getSubscriptions`, `requestProducts`, `requestSubscription`
@@ -107,7 +112,7 @@ const restored = await restorePurchases({
 import {finishTransaction, type Purchase} from 'expo-iap';
 
 function getToken(p: Purchase) {
-  return p.purchaseToken; // iOS JWS or Android token
+  return p.purchaseToken; // iOS: JWS, Android: purchaseToken
 }
 
 await finishTransaction({purchase: somePurchase, isConsumable: true});

docs/docs/api/methods/core-methods.md

@@ -13,9 +13,8 @@ import AdFitTopFixed from "@site/src/uis/AdFitTopFixed";
 This section covers the core methods available in expo-iap for managing in-app purchases.
 
 Note: expo-iap aligns with the OpenIAP API surface. For canonical cross-SDK API docs, see:
-- https://www.openiap.dev/docs/apis
 
- 
+- [OpenIAP APIs](https://www.openiap.dev/docs/apis)
 
 ## Unified APIs
 
@@ -73,10 +72,6 @@ const cleanup = async () => {
 
 **Note:** When using the `useIAP` hook, connection cleanup is automatic.
 
- 
-
- 
-
 ## fetchProducts()
 
 Fetches product or subscription information from the store.
@@ -125,8 +120,6 @@ const loadSubscriptions = async () => {
 
 [**Product Interface**](../types.md#product)
 
- 
-
 ## requestPurchase()
 
 Initiates a purchase request for products or subscriptions.
@@ -189,8 +182,6 @@ const buySubscription = async (subscriptionId: string, subscription?: any) => {
 };
 ```
 
- 
-
 ### Detailed Platform Examples
 
 #### iOS Only
@@ -244,8 +235,6 @@ For subscription status checks after a purchase or when listing entitlements:
 - iOS: Check `expirationDateIOS` to determine if the subscription is still active
 - Android: Check `autoRenewingAndroid` to see if auto‑renewal has been canceled
 
- 
-
 ## finishTransaction()
 
 Completes a purchase transaction. Must be called after successful receipt validation.
@@ -318,8 +307,6 @@ const restorePurchases = async () => {
 
 **Returns:** `Promise<Purchase[]>`
 
- 
-
 ## deepLinkToSubscriptions()
 
 Opens the platform-specific subscription management UI.
@@ -460,7 +447,6 @@ interface Purchase {
   id: string; // Transaction identifier
   productId: string;
   transactionDate: number;
-  transactionReceipt: string;
   purchaseToken?: string; // Unified token (iOS JWS or Android token)
 
   // iOS-specific properties
@@ -488,7 +474,6 @@ interface Purchase {
 
 The following iOS‑only helpers expose StoreKit and App Store specific capabilities. Most day‑to‑day flows are covered by the cross‑platform Core Methods above; use these only when you need iOS features.
 
-
 ### clearTransactionIOS()
 
 Clears all pending transactions from the iOS payment queue. Useful if your app previously crashed or missed finishing transactions.
@@ -565,7 +550,7 @@ Checks if the user is eligible for an introductory offer for a subscription grou
 import {isEligibleForIntroOfferIOS, fetchProducts} from 'expo-iap';
 
 // Example: derive group ID from a fetched subscription product
-const [sub] = await fetchProducts({ skus: ['your_sub_sku'], type: 'subs' });
+const [sub] = await fetchProducts({skus: ['your_sub_sku'], type: 'subs'});
 const groupId = sub?.subscriptionInfoIOS?.subscriptionGroupId ?? '';
 const eligible = groupId ? await isEligibleForIntroOfferIOS(groupId) : false;
 ```
@@ -710,7 +695,10 @@ const fetchAppTransaction = async () => {
     const appTransaction = await getAppTransactionIOS();
     if (appTransaction) {
       console.log('App Transaction ID:', appTransaction.appTransactionId);
-      console.log('Original Purchase Date:', new Date(appTransaction.originalPurchaseDate));
+      console.log(
+        'Original Purchase Date:',
+        new Date(appTransaction.originalPurchaseDate),
+      );
       console.log('Device Verification:', appTransaction.deviceVerification);
     }
   } catch (error) {
@@ -748,17 +736,19 @@ Acknowledge a non‑consumable purchase or subscription on Android.
 ```ts
 import {acknowledgePurchaseAndroid} from 'expo-iap';
 
-await acknowledgePurchaseAndroid({ token: purchase.purchaseToken! });
+await acknowledgePurchaseAndroid({token: purchase.purchaseToken!});
 ```
 
 Notes:
+
 - finishTransaction() calls this automatically when `isConsumable` is false. You typically do not need to call it directly.
 
 #### consumePurchaseAndroid
 
 Consume a purchase (consumables only). This marks an item as consumed so it can be purchased again.
 
 Notes:
+
 - finishTransaction() calls Android consumption automatically when `isConsumable` is true.
 - A direct JS helper is not exposed; consumption is handled internally via the native module.
 

docs/docs/api/types.md

@@ -7,7 +7,8 @@ import AdFitTopFixed from "@site/src/uis/AdFitTopFixed";
 This page contains the TypeScript types and interfaces used throughout the expo-iap library.
 
 Note: expo-iap aligns closely with the OpenIAP type schema. For canonical definitions and cross-SDK parity, see OpenIAP Types:
-- https://www.openiap.dev/docs/types
+
+- [OpenIAP Types](https://www.openiap.dev/docs/types)
 
 ## Core Types
 
@@ -75,7 +76,6 @@ interface Purchase {
   id: string; // Transaction identifier
   productId: string;
   transactionDate: number;
-  transactionReceipt: string;
   purchaseToken?: string; // Unified token (iOS JWS or Android token)
 }
 ```
@@ -156,7 +156,7 @@ The following sections describe the complete TypeScript surface for expo‑iap.
 ### Core
 
 ```ts
-export type ChangeEventPayload = { value: string };
+export type ChangeEventPayload = {value: string};
 
 // iOS detailed product types
 export enum ProductTypeIOS {
@@ -195,19 +195,18 @@ export type PurchaseCommon = {
   productId: string;
   ids?: string[];
   transactionDate: number;
-  transactionReceipt: string;
   purchaseToken?: string;
   platform?: string;
   quantity: number;
   purchaseState: PurchaseState;
   isAutoRenewing: boolean;
 };
 
-export type ProductSubscriptionCommon = ProductCommon & { type: 'subs' };
+export type ProductSubscriptionCommon = ProductCommon & {type: 'subs'};
 
 // Platform tags
-export type IosPlatform = { platform: 'ios' };
-export type AndroidPlatform = { platform: 'android' };
+export type IosPlatform = {platform: 'ios'};
+export type AndroidPlatform = {platform: 'android'};
 ```
 
 ### iOS
@@ -220,7 +219,7 @@ type SubscriptionOffer = {
   displayPrice: string;
   id: string;
   paymentMode: PaymentMode;
-  period: { unit: SubscriptionIosPeriod; value: number };
+  period: {unit: SubscriptionIosPeriod; value: number};
   periodCount: number;
   price: number;
   type: 'introductory' | 'promotional';
@@ -230,7 +229,7 @@ type SubscriptionInfo = {
   introductoryOffer?: SubscriptionOffer;
   promotionalOffers?: SubscriptionOffer[];
   subscriptionGroupId: string;
-  subscriptionPeriod: { unit: SubscriptionIosPeriod; value: number };
+  subscriptionPeriod: {unit: SubscriptionIosPeriod; value: number};
 };
 
 export type Discount = {
@@ -285,7 +284,7 @@ export type PurchaseIOS = PurchaseCommon & {
   transactionReasonIOS?: 'PURCHASE' | 'RENEWAL' | string;
   revocationDateIOS?: number;
   revocationReasonIOS?: string;
-  offerIOS?: { id: string; type: string; paymentMode: string };
+  offerIOS?: {id: string; type: string; paymentMode: string};
   currencyCodeIOS?: string;
   currencySymbolIOS?: string;
   countryCodeIOS?: string;
@@ -337,7 +336,7 @@ type PricingPhaseAndroid = {
   recurrenceMode: number;
 };
 
-type PricingPhasesAndroid = { pricingPhaseList: PricingPhaseAndroid[] };
+type PricingPhasesAndroid = {pricingPhaseList: PricingPhaseAndroid[]};
 
 type ProductSubscriptionAndroidOfferDetail = {
   basePlanId: string;
@@ -395,7 +394,7 @@ export type ProductPurchase =
   | (PurchaseIOS & IosPlatform);
 
 export type SubscriptionPurchase =
-  | (PurchaseAndroid & AndroidPlatform & { autoRenewingAndroid: boolean })
+  | (PurchaseAndroid & AndroidPlatform & {autoRenewingAndroid: boolean})
   | (PurchaseIOS & IosPlatform);
 
 export type Purchase =
@@ -430,7 +429,7 @@ export interface RequestSubscriptionAndroidProps
   extends RequestPurchaseAndroidProps {
   readonly purchaseTokenAndroid?: string;
   readonly replacementModeAndroid?: number;
-  readonly subscriptionOffers: { sku: string; offerToken: string }[];
+  readonly subscriptionOffers: {sku: string; offerToken: string}[];
 }
 
 export interface RequestPurchasePropsByPlatforms {
@@ -549,7 +548,9 @@ export interface IapContext {
     type?: 'inapp' | 'subs';
   }): Promise<Purchase | Purchase[] | void>;
 
-  finishTransaction(params: FinishTransactionParams): Promise<PurchaseResult | boolean>;
+  finishTransaction(
+    params: FinishTransactionParams,
+  ): Promise<PurchaseResult | boolean>;
 
   getAvailablePurchases(options?: PurchaseOptions): Promise<Purchase[]>;
 

docs/docs/examples/purchase-flow.md

@@ -14,7 +14,7 @@ This example walks through a clean purchase flow using expo-iap with the `useIAP
 
 View the full example source:
 
-- GitHub: https://github.com/hyochan/expo-iap/blob/main/example/app/purchase-flow.tsx
+- GitHub: [example/app/purchase-flow.tsx](https://github.com/hyochan/expo-iap/blob/main/example/app/purchase-flow.tsx)
 
 ## Flow Overview
 
@@ -36,7 +36,7 @@ View the full example source:
 
   `finishTransaction({ purchase, isConsumable })`
 
-```
+```txt
 Connect → Fetch Products → Request Purchase → Server Validate → Finish Transaction
 ```
 
@@ -77,14 +77,15 @@ Use the modern, platform‑specific request container (v2.7.0+). This avoids man
 ```tsx
 await requestPurchase({
   request: {
-    ios: { sku: productId, quantity: 1 },
-    android: { skus: [productId] },
+    ios: {sku: productId, quantity: 1},
+    android: {skus: [productId]},
   },
   type: 'inapp',
 });
 ```
 
 Notes:
+
 - Keep `andDangerouslyFinishTransactionAutomatically` off (default) to validate first.
 
 ### Key iOS Options
@@ -99,7 +100,6 @@ Purchase objects have different properties on iOS and Android. When accessing pl
 ```tsx
 // Unified fields
 const token = purchase.purchaseToken; // iOS JWS or Android token
-const receipt = purchase.transactionReceipt; // Raw receipt (iOS), useful for debugging
 
 // Android-only helpers
 // const pkg = (purchase as PurchaseAndroid).packageNameAndroid;

docs/docs/examples/subscription-flow.md

@@ -5,6 +5,7 @@ sidebar_position: 2
 ---
 
 <!-- This document was renamed from subscription-manager.md to subscription-flow.md -->
+
 import AdFitTopFixed from "@site/src/uis/AdFitTopFixed";
 
 # Subscriptions Flow
@@ -15,7 +16,7 @@ This example walks through a practical subscriptions flow with expo-iap. It mirr
 
 View the full example source:
 
-- GitHub: https://github.com/hyochan/expo-iap/blob/main/example/app/subscription-flow.tsx
+- GitHub: [example/app/subscription-flow.tsx](https://github.com/hyochan/expo-iap/blob/main/example/app/subscription-flow.tsx)
 
 ## Important: Platform-Specific Subscription Properties
 
@@ -44,7 +45,7 @@ When checking subscription status, different platforms provide different propert
 
 View the full example source:
 
-- GitHub: https://github.com/hyochan/expo-iap/blob/main/example/app/subscription-flow.tsx
+- GitHub: [example/app/subscription-flow.tsx](https://github.com/hyochan/expo-iap/blob/main/example/app/subscription-flow.tsx)
 
 ```tsx
 import React, {useEffect, useState} from 'react';
@@ -221,11 +222,9 @@ export default function SubscriptionManager() {
             'Content-Type': 'application/json',
           },
           body: JSON.stringify({
-            receipt: purchase.transactionReceipt,
             productId: purchase.productId,
-            // Platform-specific fields
             purchaseToken: purchase.purchaseToken, // Unified field (iOS: JWS, Android: purchaseToken)
-            transactionId: purchase.transactionId, // iOS
+            packageName: (purchase as PurchaseAndroid)?.packageNameAndroid, // Will be needed in android
           }),
         },
       );
@@ -710,7 +709,7 @@ await requestPurchase({
 
 Subscription validation requires different approaches:
 
-- **iOS**: Send `transactionReceipt` to Apple's validation servers
+- **iOS**: Send `purchaseToken` which was ~~`transactionReceipt`~~ to Apple's validation servers
 - **Android**: Send `purchaseToken` and `packageName` to Google Play validation
 
 This is handled in the `validateSubscriptionStatus` function with platform-specific logic.

docs/docs/guides/getting-started.md

@@ -147,7 +147,7 @@ const productIds = [
 
 useEffect(() => {
   if (connected) {
-    fetchProducts({ skus: productIds, type: 'inapp' });
+    fetchProducts({skus: productIds, type: 'inapp'});
   }
 }, [connected, fetchProducts]);
 ```
@@ -188,32 +188,18 @@ The `useIAP` hook automatically handles purchase updates. When a purchase is suc
 ```tsx
 useEffect(() => {
   if (currentPurchase) {
-    // Platform-specific validation
+    // Unified validation (iOS/Android)
     const validateAndFinish = async () => {
       try {
-        if (Platform.OS === 'ios') {
-          // iOS: Simple validation
-          await validateReceiptOnServer({
-            receiptData: currentPurchase.transactionReceipt,
-            productId: currentPurchase.productId,
-          });
-        } else if (Platform.OS === 'android') {
-          // Android: Check required parameters first
-          const purchaseToken = currentPurchase.purchaseToken;
-          const packageName = currentPurchase.packageNameAndroid;
-
-          if (!purchaseToken || !packageName) {
-            throw new Error(
-              'Android validation requires packageName and purchaseToken',
-            );
-          }
-
-          await validateReceiptOnServer({
-            packageName,
-            purchaseToken,
-            productId: currentPurchase.productId,
-          });
-        }
+        const purchaseToken = currentPurchase.purchaseToken;
+        const productId = currentPurchase.productId;
+        const packageName = currentPurchase.packageNameAndroid; // iOS: undefined
+
+        await validateReceiptOnServer({
+          productId,
+          purchaseToken,
+          ...(packageName ? {packageName} : {}),
+        });
 
         // If validation successful, finish the transaction
         await finishTransaction({purchase: currentPurchase});