Complete all the steps in the Google Pay API deploy to production documentation for Android<\/a>.<\/li>\n<\/ol>\n <\/p>\n
In the live environment, note that Google Pay will only be available if:<\/p>\n
\n- The shopper is logged in to their Google account.<\/li>\n
- The shopper has at least one valid payment method on their Google Pay account.<\/li>\n<\/ul>\n
\n
- \n Component integration guide\n <\/a><\/li>
- \n Google Pay API\n <\/a><\/li>
- \n Tokenization\n <\/a><\/li>
- \n Google Pay error codes\n <\/a><\/li>
- \n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/google-pay\/react-native-component","articleFields":{"description":"Add Google Pay to an existing Components integration.","parameters":{"integration":"Component","integration_guide_url":"react-native\/components","component_name":"Component","component_name_capitalized":"The Component","payment_method":"Google Pay","payment_method_type":"googlepay","link":"https:\/\/developers.google.com\/pay\/api\/android\/guides\/setup","merchant_id":"https:\/\/developers.google.com\/pay\/api\/android\/reference\/request-objects#MerchantInfo"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/payment-methods\/google-pay\/react-native-component","title":"Google Pay Component integration","content":"This page explains how to add Google Pay to your existing Component integration.\nWhen shoppers select Google Pay, Component presents the Google Pay payment sheet where shoppers choose a card they want to use. If shoppers select a card that requires 3D Secure authentication, Component also handles redirecting shoppers to another website to complete the verification.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built your Component integration.\n\n\nSetup steps\nBefore you begin: Follow the setup steps in the Google Pay documentation. Add Google Pay in your Customer Area..\n\n\n\nAPI reference\nYou do not need to send additional fields for Google Pay. See the \/payments endpoint API reference for the optional fields you can send.\nComponent configuration\nPass state to your Checkout activity onActivityResult:\n\n \n\nOptional configuration\nYou can optionally include the following properties when you configure AdyenCheckout:\n\n\n\nProperty\nDescription\nDefault\n\n\n\n\nmerchantAccount\nYour Google Merchant ID. This can be anything for testing. Before you go live, get your Google Merchant ID from the Google Pay & Wallet Console.\nThe corresponding merchant ID value from the brands array in the \/paymentMethods response.\n\n\nallowedCardNetworks\nThe list of allowed card networks in capital letters. The allowed networks are automatically configured based on your account settings, but you can override this here.\n-\n\n\nallowedAuthMethods\nThe list of fields that are supported to authenticate a card transaction. Possible values:- PAN_ONLY:associated with payment cards stored on file with the user's Google Account. Returned payment data includes personal account number (PAN) with the expiration month and the expiration year. -CRYPTOGRAM_3DS: associated with cards stored as Android device tokens. Returned payment data includes a 3D Secure cryptogram generated on the device.\n-\n\n\ntotalPriceStatus\nThe status of the total price. Possible values:- FINAL: the total price shown to the shopper doesn't change.- ESTIMATED: the total price can change based on the details of the response, such as sales tax based on the billing address.\nFINAL\n\n\nallowPrepaidCards\nSet to false to turn off support for prepaid cards.\ntrue: prepaid cards from supported card networks are supported.\n\n\nallowCreditCards\nSet to false to turn off support for credit cards.\ntrue\n\n\nbillingAddressRequired\nSet to true to require the shopper to enter their full billing address. Only request this if it is required to process a transaction.\nfalse\n\n\nbillingAddressParameters\nThe expected fields returned if billingAddressRequired is set to true. For more information on the available fields, see Google Pay API documentation on \n billingAddressParameters\n.\n-\n\n\nemailRequired\nSet to true to require the shopper to enter their email address.\nfalse\n\n\nshippingAddressRequired\nSet to true to require the shopper to enter their shipping address.\nfalse\n\n\nshippingAddressParameters\nThe expected fields returned if shippingAddressRequired is set to true. For more information on the available fields, see Google Pay API documentation on \n shippingAddressParameters\n.\n-\n\n\nexistingPaymentMethodRequired\nSet to true to only show the payment button if a shopper can pay with a supported payment method.The value that says if the shopper can pay with each allowed payment method comes from the IsReadyToPayResponse.paymentMethodPresent object.\nfalse\n\n\ngooglePayEnvironment\nThe environment for Google Pay. Possible values:- WalletConstants.ENVIRONMENT_TEST for test.- WalletConstants.ENVIRONMENT_TEST for live.\nThe corresponding environment to the environment you set when configuring AdyenCheckout.\n\n\n\n\nTo learn more about the optional request object options, check the Google Pay API documentation.\n\nRecurring payments\nTo make recurring Google Pay payments, you first need to create a shopper token and then make subsequent recurring transactions with the token.\nRefer to Tokenization for more information and detailed instructions.\nTest and go live\nTo start testing Google Pay, log in to a Google account and create a Google Pay wallet.\nThere are two approaches to using this wallet for testing:\n\n\nEnroll in test card suite\nEnroll your wallet in Google's test card suite. Test card suite pre-populates your wallet with a group of cards to use in the TEST environment. These are related to Adyen's collection of test cards, and cover scenarios including:\n\nCards stored as FPAN\nCards stored as DPAN (only when testing through native Android and Chrome on Android)\nCards enabled for 3DS2\n\nWhen you start the payment flow and open the list of test cards, each card is marked with the applicable scenario.\n\n\nWithout test card suite\nYou upload real credit cards to your wallet, which are mapped to one of Adyen's test cards of the same brand. Your card is not charged.\nTo test 3D Secure 2, you must use American Express or Discover cards, which trigger 3D Secure 2 challenge flows in the test environment. You cannot use any other card brands.\n\n\nYou can check the status of a Google Pay test payment in your Customer Area > Transactions > Payments, whether you used a card from the test card suite or or not. Remember that cards outside the test card suite are mapped to an Adyen test card of the same brand.\nFor more information, see\u00a0Google Pay's test environment for Android.\nBefore you go live\n\nWe recommend that you test the scenarios described in Google Pay\u2019s API reference for Android in your live environment.\n\n\nMake sure that your API credential has the API Clientside Encryption Payments role. Check this in your live Customer Area or ask your Admin user to verify.\nGo to your live Customer Area to configure your Google Merchant ID.\nComplete all the steps in the Google Pay API deploy to production documentation for Android.\n\n \nIn the live environment, note that Google Pay will only be available if:\n\nThe shopper is logged in to their Google account.\nThe shopper has at least one valid payment method on their Google Pay account.\n\n\n\n Component integration guide\n \n Google Pay API\n \n Tokenization\n \n Google Pay error codes\n \n API Explorer\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"Google Pay","lvl3":"Google Pay Component integration"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/pt\/payment-methods\/google-pay","lvl3":"\/pt\/payment-methods\/google-pay\/react-native-component"},"levels":4,"category":"Payment method","category_color":"green","tags":["Google","Component","integration"]}}