Reputation: 697
Is there any documentation as to what other fields are included in the response of the JWT postback when a transaction is completed?
I noticed from documentation HERE that an extra field is added for cancellations, ie statusCode.
Now to the point:
Does / can the postback JWT contain the email of the buyer?
Is there a field we can set when constructing the initial JWT request that will request wallet to relay the email?
In the old checkout, there was a mechanism of querying checkout with the orderID in order to retrieve the order details (and thus buyer email), is there an API in digital goods that does this too?
I'd like the email to relay activation codes when payment is completed.
Upvotes: 0
Views: 153
Reputation: 12351
This documentation is probably what you are looking for - available fields for single and subscription Jwt
Postback Jwts:
- Does / can the postback JWT contain the email of the buyer?
- Is there a field we can set when constructing the initial JWT request that will request wallet to relay the email?
sellerData
and "load it yourself" - perhaps obtain it from your app (first). You can also look into Google+ sign in (it's a separate API though, so you'l have to work that). The idea is that at the end of the day it's a Google Account
(to use/have Wallet, Google+ etc.)In the old checkout, there was a mechanism of querying checkout with the orderID in order to retrieve the order details (and thus buyer email), is there an API in digital goods that does this too?
AFAIK (I'm not a Googler) there is no current API like the one in Google Checkout - it's a wish list for me too :)
hth...
Upvotes: 1