如何获取Google Play用户购买产品的实际支付金额？Android Publisher相关技术咨询
Great question—this is a common pain point for developers since the standard purchase details objects from the Android Publisher API don’t explicitly include the user’s actual out-of-pocket payment amount. Luckily, there are a couple of reliable ways to access this historical transaction data:
1. Use the Google Play Developer API's Order Reports Endpoints
The Order Reports suite of the Google Play Developer API is built specifically to expose financial transaction details, including the exact amount a user paid (accounting for discounts, promotions, regional pricing, or any other adjustments that might make it lower than the product’s current listed price).
You’ll want to leverage the orders.list endpoint, which returns order objects containing key fields like:
paymentAmountMicros: The total amount the user actually paid, represented in micros of the order’s currency (e.g.,999000equals $9.99 USD)paymentCurrencyCode: The 3-letter ISO currency code for the transaction
To use this endpoint, you’ll need the https://www.googleapis.com/auth/androidpublisher OAuth scope, and you can filter results by date range, order status, or product type to narrow down to the specific transactions you need.
2. Export Order Data Directly from the Google Play Console
If you don’t need real-time access or are working with bulk historical data, you can export full order reports as CSV files directly from the Play Console:
- Navigate to Revenue > Orders in your Play Console dashboard
- Use the built-in filters to select your target date range, product types, or order statuses
- Click the Export button to download a CSV that includes clear columns for the user’s actual payment amount, currency, discount details, and other transaction metadata
This is a quick, no-code way to reconcile payments or analyze historical purchase trends.
3. Subscription-Specific Notes
For subscription products, you can cross-reference the subscription’s billing event history (via the Purchases.subscriptionsv2:get endpoint) with order report data to track recurring payments. While the v2 subscription API provides details about billing cycles and status changes, the actual user payment amount is still most reliably retrieved from the order reports.
Context on the Stadia Reference
You mentioned that Stadia’s "Purchases & Subscriptions" page displays historical actual payment amounts—this is because Stadia’s backend integrates with the same Google payment order dataset that’s available to Play Store developers via the methods above. The data you’ll access will match that historical transaction record, not the product’s current listed price.
内容的提问来源于stack exchange，提问作者Roc Boronat
