Mixing
Google Pay in Android application Api 1 vs Api 2
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have go through this integration tutorial on Stripe website where there is shown Google Pay integration I assume in Api version 1.
https://stripe.com/docs/mobile/android/google-pay
But now I have found that from July 2018 there is new Api version 2 for Google Pay.
https://developers.google.com/pay/api/android/guides/tutorial
I can see this new api is more JSON based using string key-values rather than strongly typed constraints.
Is Api version 1 deprecated?
Is there Api version 2 strongly-typed equivalent for Android?
Will Stripe support Api version 2?
What I lose if I stay with Api version 1? Will for instance 3D secure cards work? or version number doesn't matter from client perspective?
I can see this are some new things:
private static JSONArray getAllowedCardAuthMethods() {
return new JSONArray()
.put("PAN_ONLY")
.put("CRYPTOGRAM_3DS");
}
android stripe-payments google-pay asked Jan 3 at 9:24
Michał ZiobroMichał Ziobro
1,65612334
add a comment |
I have go through this integration tutorial on Stripe website where there is shown Google Pay integration I assume in Api version 1.
https://stripe.com/docs/mobile/android/google-pay
But now I have found that from July 2018 there is new Api version 2 for Google Pay.
https://developers.google.com/pay/api/android/guides/tutorial
I can see this new api is more JSON based using string key-values rather than strongly typed constraints.
Is Api version 1 deprecated?
Is there Api version 2 strongly-typed equivalent for Android?
Will Stripe support Api version 2?
What I lose if I stay with Api version 1? Will for instance 3D secure cards work? or version number doesn't matter from client perspective?
I can see this are some new things:
private static JSONArray getAllowedCardAuthMethods() {
return new JSONArray()
.put("PAN_ONLY")
.put("CRYPTOGRAM_3DS");
}
asked Jan 3 at 9:24
Michał ZiobroMichał Ziobro
1,65612334
add a comment |
I have go through this integration tutorial on Stripe website where there is shown Google Pay integration I assume in Api version 1.
https://stripe.com/docs/mobile/android/google-pay
But now I have found that from July 2018 there is new Api version 2 for Google Pay.
https://developers.google.com/pay/api/android/guides/tutorial
I can see this new api is more JSON based using string key-values rather than strongly typed constraints.
Is Api version 1 deprecated?
Is there Api version 2 strongly-typed equivalent for Android?
Will Stripe support Api version 2?
What I lose if I stay with Api version 1? Will for instance 3D secure cards work? or version number doesn't matter from client perspective?
I can see this are some new things:
private static JSONArray getAllowedCardAuthMethods() {
return new JSONArray()
.put("PAN_ONLY")
.put("CRYPTOGRAM_3DS");
}
asked Jan 3 at 9:24
Michał ZiobroMichał Ziobro
1,65612334
I have go through this integration tutorial on Stripe website where there is shown Google Pay integration I assume in Api version 1.
https://stripe.com/docs/mobile/android/google-pay
But now I have found that from July 2018 there is new Api version 2 for Google Pay.
https://developers.google.com/pay/api/android/guides/tutorial
I can see this new api is more JSON based using string key-values rather than strongly typed constraints.
Is Api version 1 deprecated?
Is there Api version 2 strongly-typed equivalent for Android?
Will Stripe support Api version 2?
What I lose if I stay with Api version 1? Will for instance 3D secure cards work? or version number doesn't matter from client perspective?
I can see this are some new things:
private static JSONArray getAllowedCardAuthMethods() {
return new JSONArray()
.put("PAN_ONLY")
.put("CRYPTOGRAM_3DS");
}
asked Jan 3 at 9:24
Michał ZiobroMichał Ziobro
1,65612334
asked Jan 3 at 9:24
Michał ZiobroMichał Ziobro
1,65612334
asked Jan 3 at 9:24
Michał ZiobroMichał Ziobro
1,65612334
asked Jan 3 at 9:24
Michał ZiobroMichał Ziobro
1,65612334
asked Jan 3 at 9:24
Michał ZiobroMichał Ziobro
1,65612334
1,65612334
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Is Api version 1 deprecated?
No. Not yet at least.
Is there Api version 2 strongly-typed equivalent for Android?
The current API affords both object builder and json e.g. IsReadyToPayRequest.newBuilder() or IsReadyToPayRequest.fromJson(), however json is the new preferred method and offers additional features:
Key point: The new JSON-based request objects include features and functionality not available to apps that use the previous Builder implementation.
"In the previous version of the Google Pay API, the Builder object we used only supported cards as a form of payment for IsReadyToPayRequest or PaymentDataRequest. In the latest version of the Google Pay API, the CARD payment method is only one of multiple possible payment methods for IsReadyToPayRequest or PaymentDataRequest."
What I lose if I stay with Api version 1? Will for instance 3D secure
cards work? or version number doesn't matter from client perspective?
https://developers.google.com/pay/api/android/guides/resources/update-to-latest-version
details the transition between builder and json APIs, including tokenized cards:
If your app supported PAYMENT_METHOD_TOKENIZED_CARD:
Add "CRYPTOGRAM_3DS" to the allowedAuthMethods array.
so 3DS was/is available with builder API via WalletConstants.PAYMENT_METHOD_TOKENIZED_CARD
answered Jan 3 at 10:40
veritas1veritas1
4,64741632
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%2f54019409%2fgoogle-pay-in-android-application-api-1-vs-api-2%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
Is Api version 1 deprecated?
No. Not yet at least.
Is there Api version 2 strongly-typed equivalent for Android?
The current API affords both object builder and json e.g. IsReadyToPayRequest.newBuilder() or IsReadyToPayRequest.fromJson(), however json is the new preferred method and offers additional features:
Key point: The new JSON-based request objects include features and functionality not available to apps that use the previous Builder implementation.
"In the previous version of the Google Pay API, the Builder object we used only supported cards as a form of payment for IsReadyToPayRequest or PaymentDataRequest. In the latest version of the Google Pay API, the CARD payment method is only one of multiple possible payment methods for IsReadyToPayRequest or PaymentDataRequest."
What I lose if I stay with Api version 1? Will for instance 3D secure
cards work? or version number doesn't matter from client perspective?
https://developers.google.com/pay/api/android/guides/resources/update-to-latest-version
details the transition between builder and json APIs, including tokenized cards:
If your app supported PAYMENT_METHOD_TOKENIZED_CARD:
Add "CRYPTOGRAM_3DS" to the allowedAuthMethods array.
so 3DS was/is available with builder API via WalletConstants.PAYMENT_METHOD_TOKENIZED_CARD
answered Jan 3 at 10:40
veritas1veritas1
4,64741632
add a comment |
Is Api version 1 deprecated?
No. Not yet at least.
Is there Api version 2 strongly-typed equivalent for Android?
The current API affords both object builder and json e.g. IsReadyToPayRequest.newBuilder() or IsReadyToPayRequest.fromJson(), however json is the new preferred method and offers additional features:
Key point: The new JSON-based request objects include features and functionality not available to apps that use the previous Builder implementation.
"In the previous version of the Google Pay API, the Builder object we used only supported cards as a form of payment for IsReadyToPayRequest or PaymentDataRequest. In the latest version of the Google Pay API, the CARD payment method is only one of multiple possible payment methods for IsReadyToPayRequest or PaymentDataRequest."
What I lose if I stay with Api version 1? Will for instance 3D secure
cards work? or version number doesn't matter from client perspective?
https://developers.google.com/pay/api/android/guides/resources/update-to-latest-version
details the transition between builder and json APIs, including tokenized cards:
If your app supported PAYMENT_METHOD_TOKENIZED_CARD:
Add "CRYPTOGRAM_3DS" to the allowedAuthMethods array.
so 3DS was/is available with builder API via WalletConstants.PAYMENT_METHOD_TOKENIZED_CARD
answered Jan 3 at 10:40
veritas1veritas1
4,64741632
add a comment |
Is Api version 1 deprecated?
No. Not yet at least.
Is there Api version 2 strongly-typed equivalent for Android?
The current API affords both object builder and json e.g. IsReadyToPayRequest.newBuilder() or IsReadyToPayRequest.fromJson(), however json is the new preferred method and offers additional features:
Key point: The new JSON-based request objects include features and functionality not available to apps that use the previous Builder implementation.
"In the previous version of the Google Pay API, the Builder object we used only supported cards as a form of payment for IsReadyToPayRequest or PaymentDataRequest. In the latest version of the Google Pay API, the CARD payment method is only one of multiple possible payment methods for IsReadyToPayRequest or PaymentDataRequest."
What I lose if I stay with Api version 1? Will for instance 3D secure
cards work? or version number doesn't matter from client perspective?
https://developers.google.com/pay/api/android/guides/resources/update-to-latest-version
details the transition between builder and json APIs, including tokenized cards:
If your app supported PAYMENT_METHOD_TOKENIZED_CARD:
Add "CRYPTOGRAM_3DS" to the allowedAuthMethods array.
so 3DS was/is available with builder API via WalletConstants.PAYMENT_METHOD_TOKENIZED_CARD
answered Jan 3 at 10:40
veritas1veritas1
4,64741632
Is Api version 1 deprecated?
No. Not yet at least.
Is there Api version 2 strongly-typed equivalent for Android?
The current API affords both object builder and json e.g. IsReadyToPayRequest.newBuilder() or IsReadyToPayRequest.fromJson(), however json is the new preferred method and offers additional features:
Key point: The new JSON-based request objects include features and functionality not available to apps that use the previous Builder implementation.
"In the previous version of the Google Pay API, the Builder object we used only supported cards as a form of payment for IsReadyToPayRequest or PaymentDataRequest. In the latest version of the Google Pay API, the CARD payment method is only one of multiple possible payment methods for IsReadyToPayRequest or PaymentDataRequest."
What I lose if I stay with Api version 1? Will for instance 3D secure
cards work? or version number doesn't matter from client perspective?
https://developers.google.com/pay/api/android/guides/resources/update-to-latest-version
details the transition between builder and json APIs, including tokenized cards:
If your app supported PAYMENT_METHOD_TOKENIZED_CARD:
Add "CRYPTOGRAM_3DS" to the allowedAuthMethods array.
so 3DS was/is available with builder API via WalletConstants.PAYMENT_METHOD_TOKENIZED_CARD
answered Jan 3 at 10:40
veritas1veritas1
4,64741632
answered Jan 3 at 10:40
veritas1veritas1
4,64741632
answered Jan 3 at 10:40
veritas1veritas1
4,64741632
answered Jan 3 at 10:40
veritas1veritas1
4,64741632
4,64741632
add a comment |
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.
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%2f54019409%2fgoogle-pay-in-android-application-api-1-vs-api-2%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
