Safe to assume paymentState is absent from Google Play API for test purchases?

Question

It appears when I get the Purchases.subscriptions resource for a purchaseToken using the Google Play Developer API that test purchases do not include the paymentState property. However, real purchases seem to always include it. So is it safe to assume that when a Purchases.subscriptions resource does not include the paymentState property that that purchaseToken was from a test purchase?

We are validating purchaseTokens and renewals server-side and are looking for a better solution for determining if a purchase was a test purchase or not without having to depend on the presence or absence of an orderId which is only available to the app.

Answer 1

since July 10th 2017, Google Play now provides an orderID from test purchases.