Your Digital Media Has Never Looked So Good

 
sldev
Topic Author
Posts: 1
Joined: Mon Oct 17, 2016 8:55 am

Transaction API "purchaseDate" value always same as "originalPurchaseDate"?

Mon Oct 17, 2016 9:25 am

I'm working with the transaction API, but the the "purchaseDate" and "originalPurchaseDate" values are not what I expected.

The documentation at https://sdkdocs.roku.com/display/sdkdoc/Web+Service+API isn't very explicit, but the sample response suggests that the "purchaseDate" will be the start of the current billing period (i.e. a billing cycle before the expirationDate):

  <purchaseDate>2012-07-22T14:59:50</purchaseDate>
  <expirationDate>2012-08-22T14:59:50</expirationDate>
  <originalPurchaseDate>2010-08-22T14:59:50</originalPurchaseDate>


But in all the real-world responses I've seen, the purchaseDate is the same as the originalPurchaseDate, even when multiple billing cycles have completed.  Here's an excerpt from the actual response I get:

  <expirationDate>2016-11-11T23:49:26</expirationDate>
  <originalPurchaseDate>2016-04-11T23:49:26</originalPurchaseDate>
  <purchaseDate>2016-04-11T23:49:26</purchaseDate>



This looks like an error in the API - can anyone confirm this is broken?  Any plans to fix?
 
auzy
Posts: 29
Joined: Tue Sep 28, 2010 1:20 pm

Re: Transaction API "purchaseDate" value always same as "originalPurchaseDate"?

Mon Nov 05, 2018 10:16 am

I'm seeing the same issue, and makes it difficult to determine when the last charge occurred.  Is there any way to determine this?

Who is online

Users browsing this forum: No registered users and 3 guests