expirationYear: This is set five years from the current year.
messageId: This is randomly generated for each payload.messageExpiration: This is set one week from the current time.The following three fields might differ in your decrypted payload compared to the samples below: The payload for non-tokenized cards is always the same, regardless of the card network. In addition, the payload for tokenized cards is different, which depends upon the card The payload structureĭepends on whether the card that was selected is tokenized, which means added to Google Pay. Once the sample token is decrypted, you receive the cleartext payload. Decrypted payload Important: The payload samples provided here are illustrative only. When you build a PaymentMethodTokenRecipient object. fetchSenderVerifyingKeysWith(GooglePaymentsPublicKeysManager.INSTANCE_TEST) is set The tokens produced in ENVIRONMENT_TEST are encrypted with your test public key that Install and add at least one supported payment method to the Google Pay app. Generate sample tokens for tokenized cards, you need to Important: Your real card details are never used when inĪdd at least one chargeable card to your Google Account before you proceed. However, it never actually returns real informationįrom the card that was selected, and instead, the token that results always has a constant That the user selects one of their real cards. When the PaymentsClient instance is constructed with the environment set toĮNVIRONMENT_TEST, the calls to loadPaymentData work as usual and request Sample tokens if you set ENVIRONMENT_TEST when you construct a
Generate sample tokensįor direct integrations, in order to test token decryption on your server, you can generate
This page describes how to use sample tokens to test your integration.
0 kommentar(er)
