Android Billing Client library : How to specify Developer Payload(extra data)
I am trying to use the new Android Billing Client library(1.0)
Previously, while trying to perform a purchase, there was option to add extra data to the intent.
However, when using the new library, things have been simplified to a great degree. But is there way to add the developer payload(extra string) to the purchase flow ?
android play-billing-library
add a comment |
I am trying to use the new Android Billing Client library(1.0)
Previously, while trying to perform a purchase, there was option to add extra data to the intent.
However, when using the new library, things have been simplified to a great degree. But is there way to add the developer payload(extra string) to the purchase flow ?
android play-billing-library
add a comment |
I am trying to use the new Android Billing Client library(1.0)
Previously, while trying to perform a purchase, there was option to add extra data to the intent.
However, when using the new library, things have been simplified to a great degree. But is there way to add the developer payload(extra string) to the purchase flow ?
android play-billing-library
I am trying to use the new Android Billing Client library(1.0)
Previously, while trying to perform a purchase, there was option to add extra data to the intent.
However, when using the new library, things have been simplified to a great degree. But is there way to add the developer payload(extra string) to the purchase flow ?
android play-billing-library
android play-billing-library
edited Mar 27 at 20:25
asked Mar 27 at 19:58
rgv
7431931
7431931
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Found the answer to it, the names have been changed, hence the confusion.
The BillingFlowParams builder, exposes a function named setAccountId(String accountId)
. The definition for this function is :
Specify an optional obfuscated string that is uniquely associated with the user's account in
your app.
If you pass this value, Google Play can use it to detect irregular activity, such as many
devices making purchases on the same account in a short period of time. Do not use the
developer ID or the user's Google ID for this field. In addition, this field should not
contain the user's ID in cleartext. We recommend that you use a one-way hash to generate a
string from the user's ID and store the hashed string in this field.
I think this is the new way to specify developer payload, or any extra string for extra layer of validation.
So the code will look something like this :
private fun makePurchaseFromGoogle(developerPayload : String) {
val purchaseParams = BillingFlowParams.newBuilder()
.setSku(product.sku)
.setType(product.type)
.setAccountId(developerPayload) // dev-payload
.build()
googleBillingClient.launchBillingFlow(activity, purchaseParams)
}
1
How do you retrieve it?
– Racu
Jul 6 at 20:01
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f49521453%2fandroid-billing-client-library-how-to-specify-developer-payloadextra-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Found the answer to it, the names have been changed, hence the confusion.
The BillingFlowParams builder, exposes a function named setAccountId(String accountId)
. The definition for this function is :
Specify an optional obfuscated string that is uniquely associated with the user's account in
your app.
If you pass this value, Google Play can use it to detect irregular activity, such as many
devices making purchases on the same account in a short period of time. Do not use the
developer ID or the user's Google ID for this field. In addition, this field should not
contain the user's ID in cleartext. We recommend that you use a one-way hash to generate a
string from the user's ID and store the hashed string in this field.
I think this is the new way to specify developer payload, or any extra string for extra layer of validation.
So the code will look something like this :
private fun makePurchaseFromGoogle(developerPayload : String) {
val purchaseParams = BillingFlowParams.newBuilder()
.setSku(product.sku)
.setType(product.type)
.setAccountId(developerPayload) // dev-payload
.build()
googleBillingClient.launchBillingFlow(activity, purchaseParams)
}
1
How do you retrieve it?
– Racu
Jul 6 at 20:01
add a comment |
Found the answer to it, the names have been changed, hence the confusion.
The BillingFlowParams builder, exposes a function named setAccountId(String accountId)
. The definition for this function is :
Specify an optional obfuscated string that is uniquely associated with the user's account in
your app.
If you pass this value, Google Play can use it to detect irregular activity, such as many
devices making purchases on the same account in a short period of time. Do not use the
developer ID or the user's Google ID for this field. In addition, this field should not
contain the user's ID in cleartext. We recommend that you use a one-way hash to generate a
string from the user's ID and store the hashed string in this field.
I think this is the new way to specify developer payload, or any extra string for extra layer of validation.
So the code will look something like this :
private fun makePurchaseFromGoogle(developerPayload : String) {
val purchaseParams = BillingFlowParams.newBuilder()
.setSku(product.sku)
.setType(product.type)
.setAccountId(developerPayload) // dev-payload
.build()
googleBillingClient.launchBillingFlow(activity, purchaseParams)
}
1
How do you retrieve it?
– Racu
Jul 6 at 20:01
add a comment |
Found the answer to it, the names have been changed, hence the confusion.
The BillingFlowParams builder, exposes a function named setAccountId(String accountId)
. The definition for this function is :
Specify an optional obfuscated string that is uniquely associated with the user's account in
your app.
If you pass this value, Google Play can use it to detect irregular activity, such as many
devices making purchases on the same account in a short period of time. Do not use the
developer ID or the user's Google ID for this field. In addition, this field should not
contain the user's ID in cleartext. We recommend that you use a one-way hash to generate a
string from the user's ID and store the hashed string in this field.
I think this is the new way to specify developer payload, or any extra string for extra layer of validation.
So the code will look something like this :
private fun makePurchaseFromGoogle(developerPayload : String) {
val purchaseParams = BillingFlowParams.newBuilder()
.setSku(product.sku)
.setType(product.type)
.setAccountId(developerPayload) // dev-payload
.build()
googleBillingClient.launchBillingFlow(activity, purchaseParams)
}
Found the answer to it, the names have been changed, hence the confusion.
The BillingFlowParams builder, exposes a function named setAccountId(String accountId)
. The definition for this function is :
Specify an optional obfuscated string that is uniquely associated with the user's account in
your app.
If you pass this value, Google Play can use it to detect irregular activity, such as many
devices making purchases on the same account in a short period of time. Do not use the
developer ID or the user's Google ID for this field. In addition, this field should not
contain the user's ID in cleartext. We recommend that you use a one-way hash to generate a
string from the user's ID and store the hashed string in this field.
I think this is the new way to specify developer payload, or any extra string for extra layer of validation.
So the code will look something like this :
private fun makePurchaseFromGoogle(developerPayload : String) {
val purchaseParams = BillingFlowParams.newBuilder()
.setSku(product.sku)
.setType(product.type)
.setAccountId(developerPayload) // dev-payload
.build()
googleBillingClient.launchBillingFlow(activity, purchaseParams)
}
answered Mar 27 at 20:03
rgv
7431931
7431931
1
How do you retrieve it?
– Racu
Jul 6 at 20:01
add a comment |
1
How do you retrieve it?
– Racu
Jul 6 at 20:01
1
1
How do you retrieve it?
– Racu
Jul 6 at 20:01
How do you retrieve it?
– Racu
Jul 6 at 20:01
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f49521453%2fandroid-billing-client-library-how-to-specify-developer-payloadextra-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown