Get Started with Google Pay

Google Pay lets shoppers pay with the cards saved to their Google account. Unlike Apple Pay, Google Pay doesn't require per-domain validation — Plexy's gateway (gateway: 'plexy') handles tokenization, so you only enable the payment method and render the button.

Platform support: Google Pay is available on Web and Android. On iOS in-app Google Pay is not supported — use Apple Pay instead.

Prerequisites

Before you begin:

Plexy account & Client key — get your Client key from the Plexy dashboard. It's required for Drop-in/Components to talk to the Plexy API.

Google Pay & Wallet Business Console account — create a business profile so your brand is shown in the payment sheet.

Sign in to the Google Pay & Wallet Console with your company Google account and complete the business profile (legal business name, website, and support contact details). Once the profile is filled in, open the Google Pay API section and submit your integration for review — Google checks that your checkout follows the Google Pay brand and UX guidelines before granting production access. After you submit, you'll receive a Merchant ID, which you configure in your Plexy Customer Area.

TEST environment works immediately — you can develop and test the full flow before submitting anything.

PRODUCTION payments are blocked until Google approves your submission, so plan for a review period (typically a few business days). Until approval lands, keep using the TEST environment.

Web setup

Unlike Apple Pay, Google Pay needs no separate domain-registration step. You create the Google Pay component, check availability, and mount the button into your page yourself.

1. Create the checkout and the Google Pay component

2. Check availability and mount

In the TEST environment Google Pay is always considered available.

Merchant identifiers — configure them yourself

The Web SDK does not receive any Google Pay configuration from the API. You must set every value manually in code by passing a configuration object to the component:

Field	Meaning	Required
`gatewayMerchantId`	Your Plexy merchant account — the identifier the Plexy gateway recognizes. Google does not issue or validate it; it's placed in the gateway `tokenizationSpecification` and forwarded to Plexy to route the token to the right merchant. Take this value from your Plexy Dashboard settings, where it's labeled `merchantName`.	Yes
`merchantId`	Your Google-issued merchant ID (from the Google Pay Business Console). Used by Google to identify the merchant and render the sheet	Yes — always. The SDK throws `IMPLEMENTATION_ERROR "Missing merchantId"` if absent, in both TEST and PRODUCTION
`merchantName`	Display name rendered in the payment sheet	No
`merchantOrigin` / `authJwt`	Platform / fully-qualified-domain options	No

The Plexy gateway is fixed (gateway: 'plexy') and built into the SDK — you never set it. Pass the Google environment ('TEST' / 'PRODUCTION') to the component. If omitted, it's resolved from the checkout environment: production / live / live-au / live-apse / live-us / live-in → PRODUCTION, everything else (including test) → TEST.

Native setup (Android)

1. Enable the Google Pay API in `AndroidManifest.xml`

Add this metadata tag inside your <application> element:

<meta-data
  android:name="com.google.android.gms.wallet.api.enabled"
  android:value="true" />

2a. React Native

Google Pay config is a googlepay sub-object inside the unified checkout Configuration. Required: countryCode and amount (Google Pay needs both to display the sheet).

Notes:

merchantAccount — your Plexy merchant account (the equivalent of the Web gatewayMerchantId). Take this value from your Plexy Dashboard settings, where it's labeled merchantName.

googlePayEnvironment — GooglePayEnvironment.Test or GooglePayEnvironment.Production. If omitted, inherited from the root environment (test → TEST, live-* → PRODUCTION).

totalPriceStatus — defaults to "FINAL".

The React Native config exposes no merchantId / merchantName / gateway fields. The native Android SDK supplies the Google merchantInfo and the Plexy gateway internally — on this layer you set merchantAccount (your Plexy Dashboard merchantName).

2b. Flutter

Google Pay config is the typed GooglePayConfiguration, wrapped by GooglePayComponentConfiguration (which carries the root environment / clientKey / countryCode / amount).

Unlike Web/React Native, Flutter sets the Google Pay environment explicitly via the GooglePayEnvironment enum (test / production) rather than deriving it from the environment string. Flutter is also the only mobile SDK that lets you set the Google merchantInfo (merchantId + merchantName) directly.

Configuration parameters (Android: React Native & Flutter)

Parameter	Description	Default
`merchantAccount`	Your Plexy merchant account put in the token sent to Plexy (= Web `gatewayMerchantId`). From the Plexy Dashboard settings (`merchantName`)	set manually
`merchantInfo` (Flutter only)	Google identity shown in the sheet: `merchantId` + `merchantName`	not set
`googlePayEnvironment`	Google Pay environment	from root `environment` (RN) / explicit enum (Flutter)
`totalPriceStatus`	`NOT_CURRENTLY_KNOWN` / `ESTIMATED` / `FINAL`	`FINAL`
`allowedCardNetworks`	Supported card networks	SDK default
`allowedAuthMethods`	`PAN_ONLY` / `CRYPTOGRAM_3DS`	SDK default
`allowCreditCards` / `allowPrepaidCards`	Support for credit/prepaid cards	`true`
`billingAddressRequired` (+ `billingAddressParameters`)	Request billing address	`false`
`shippingAddressRequired` (+ `shippingAddressParameters`)	Request shipping address	`false`
`emailRequired`	Request email	`false`
`existingPaymentMethodRequired`	Report shopper readiness to pay	`false`

Troubleshooting

Symptom	Likely cause / fix
PRODUCTION shows "not enabled"	Your Google Pay & Wallet Business Console submission hasn't been approved yet. Use `TEST` until approved.
Button doesn't appear	The device/browser doesn't support Google Pay, or `isAvailable()` rejected. On Web, check the console warning from the `.catch()`.
Button missing on Android	Verify the `com.google.android.gms.wallet.api.enabled` metadata tag is inside `<application>` in `AndroidManifest.xml`.
"Google Pay is unavailable on this device" (Flutter)	No Google Pay support / no saved cards; the `unavailableWidget` is shown by design.
iOS shows no Google Pay button	Expected — Google Pay is not available in-app on iOS. Use Apple Pay.
Sheet shows wrong amount/currency	Ensure `amount` and `countryCode` are both set (required together for Google Pay).

Appendix: Merchant identifiers & gateway — terminology across SDKs

There are two different "merchant" concepts, plus a fixed gateway. They are named differently per SDK:

Concept	What it is	Web	React Native	Flutter
Plexy merchant account	Your account on Plexy's side. Sent to Google as the gateway `gatewayMerchantId` and forwarded to Plexy to route the token — not issued or validated by Google. Found in the Plexy Dashboard settings under `merchantName`	`configuration.gatewayMerchantId`	`googlepay.merchantAccount`	`merchantAccount`
Google merchant identity	Google-issued identity from the Google Pay Business Console, shown in the payment sheet (`merchantId` + `merchantName`)	`configuration.merchantId` / `merchantName`	not exposed (handled natively)	`merchantInfo.merchantId` / `merchantName`
Gateway	The payment gateway Google tokenizes for	fixed `'plexy'` (internal)	internal	internal

Key points verified against the SDK source:

The gateway is always 'plexy' and is never set by you (only literally present in the Web SDK's internal request).

On Web all merchant identifiers are configured manually in code — the SDK receives nothing from the API. merchantId is required: the component throws "Missing merchantId" if absent (TEST and PRODUCTION).

On React Native only merchantAccount exists; Google's merchantInfo is supplied by the native Android SDK.

The Plexy merchant account (gatewayMerchantId / merchantAccount) comes from the Plexy Dashboard settings, where it's labeled merchantName.

Google Pay Integration

Get Started with Google Pay#

Prerequisites#

Web setup#

1. Create the checkout and the Google Pay component#

2. Check availability and mount#

Merchant identifiers — configure them yourself#

Native setup (Android)#

1. Enable the Google Pay API in AndroidManifest.xml#

2a. React Native#

2b. Flutter#

Configuration parameters (Android: React Native & Flutter)#

Troubleshooting#

Appendix: Merchant identifiers & gateway — terminology across SDKs#