> ## Documentation Index > Fetch the complete documentation index at: https://docs.wegive.com/llms.txt > Use this file to discover all available pages before exploring further. # Setting Up Google Pay via VGS > WeGive Help Center article: Set up Google Pay for your WeGive donation checkout through Very Good Security (VGS) This page describes a separate Google Pay setup path from the one in [Connecting a Payment Processor](/external/support/settings/connecting-a-payment-processor) — that page covers Google Pay enabled through a **connected Stripe account**. This page covers Google Pay enabled through **Very Good Security (VGS)**, WeGive's own payment-tokenization gateway, which does not require your organization to connect its own Stripe account. Confirm with your WeGive contact which path applies to your organization before starting — they're configured differently on both the Google side and the WeGive dashboard side. This guide walks you through creating your organization's Google Pay business profile, submitting your donation websites for review, and sharing your approved setup with WeGive. You complete the Google account and website approval steps. WeGive handles the checkout integration and connects Google Pay to your organization's payment setup. **Before starting:** confirm with your WeGive contact that Google Pay through VGS is the right setup for your organization. Coordinate a test checkout and screenshots with WeGive before submitting your websites. WeGive will confirm availability and activation after the required approvals and technical setup are complete. ## What you will need * A Google account managed by your organization, with an email address your team monitors. * Your organization's business details and donor support contact information. * The exact domains where donors use your WeGive checkout. * A working HTTPS website with WeGive installed. * Screenshots of your donation flow, including the Google Pay payment window and confirmation page. ## 1. Open the Google Pay & Wallet Console 1. Go to [pay.google.com/business](https://pay.google.com/business). If necessary, open the [Google Pay & Wallet Console](https://pay.google.com/business/console). 2. Sign in with your organization's Google account. 3. Create a business for your organization, or select its existing business from the account selector at the top of the page. 4. If asked for **Type of business**, choose **Merchant**. 5. Complete the account prompts and accept the applicable terms. Use your organization's identity throughout this process. Your organization is the merchant receiving donations; WeGive provides your donation checkout. See [Google's profile setup instructions](https://developers.google.com/pay/api/web/guides/test-and-deploy/publish-your-integration#create-your-profile). ## 2. Complete your Business Profile Select **Business Profile** in the left navigation. Under **Business identity**, select the Google payments profile for your organization or create one using the requested legal details. Use a profile with the correct organization and country. Complete **Business information**: | Field | What to enter | | - | - | | Public business name | The nonprofit name your donors recognize. | | Merchant Category Code (MCC) | Your organization's applicable category. Ask your finance team or payment processor if you are unsure. | | Corporate website / business website | Your organization's main website. | | Customer support URL | Your donor support or contact page. | | Customer support email | An inbox your donor support team monitors. | | Customer support phone | Your donor support phone number. | | Logo, if supplied | Your organization's logo, following the size requirements shown in the Console. | Finish any additional fields Google requires for your country, save the profile, and complete any requested verification. Check that its status becomes **Approved**. Google's [Business Profile help](https://support.google.com/console/answer/10877772) explains the fields and status labels. You will also submit each donation website in the next steps. Business Profile approval alone does not activate Google Pay on those websites. ## 3. Add a web integration for each checkout domain ### Prepare your domain list List the exact hostnames where your WeGive donation checkout runs. Include the subdomain, such as `giving.example.org`. | Example | What to submit | | - | - | | Checkout at `giving.example.org` | A website integration for `giving.example.org`. | | Another checkout at `donate.example.org` | A separate website integration for `donate.example.org`. | | Checkouts at `www.example.org` and `example.org` | Include each hostname that actually hosts the checkout. | | Several donation pages under `giving.example.org` | List that hostname once; individual page paths are not separate domains. | | A staging checkout at `giving-stg.example.org` | List it separately if WeGive confirms it needs Google production access. | Each domain hosting Google Pay needs individual approval. Wildcards such as `*.example.org` do not cover all your subdomains. See [Google's domain approval requirements](https://developers.google.com/pay/api/faq). If WeGive is embedded in your website or a Donate link opens a checkout on a different domain, send both URLs to WeGive. WeGive will help identify the domains to submit for your installation. ### Create the first website entry 1. Select **Google Pay API** in the left navigation. 2. If shown, choose **Get Started** and accept the Google Pay API terms. 3. Open **Integrations**. 4. In the **Web integration** card, select **Add a website**. Some Console versions call this **Add website** under **Integrate with your website**. 5. In **Website URL**, enter the exact checkout hostname, for example `giving.example.org`. Follow the field's URL format if it requests `https://`. The website must use HTTPS. Include the actual subdomain; do not replace it with the parent domain. 6. Set **Integration type** to **Gateway**. 7. If Google asks which gateway you use, choose **Very Good Security (VGS)**. This is the gateway used by this WeGive Google Pay integration. WeGive manages the VGS connection. Google lists Very Good Security as a [supported gateway](https://developers.google.com/pay/api/web/reference/request-objects#gateway). If you reach a page asking for encryption keys or a Direct integration, return to the website entry and select **Gateway**. **Add one website at a time.** The form has a single Website URL field. Complete this website's submission, return to **Integrations**, and use **Add a website** again for the next domain. Keep the entries under the appropriate organization business account. ## 4. Upload screenshots of your donation flow The form calls this section **Screenshots of your buyflow**. For a nonprofit, these are screenshots of the donation experience. Capture your organization's actual WeGive checkout with its own branding. The Google Console setup pages themselves are not the donation screenshots Google is requesting. ### What to upload in each slot | Google screenshot slot | What to capture in WeGive | Suggested filename | | - | - | - | | **Item selection** | The donation page where the donor chooses the gift amount, frequency, or fund. | `01-donation-selection.png` | | **Pre-purchase screen** | The checkout or review screen showing the donation details and total before submission. Include the selected frequency if displayed. | `02-donation-review.png` | | **Payment method screen** | The payment section after selecting Google Pay, including the Google Pay button where it appears in your checkout. | `03-google-pay-selection.png` | | **Google Pay API payment screen** | The Google Pay window that opens after clicking the button, showing the donor's Google Pay payment choice. Capture this window itself. | `04-google-pay-window.png` | | **Post-purchase screen** | The successful donation confirmation or thank-you page reached after the agreed test flow. | `05-donation-confirmation.png` | For a **single-page checkout**, several stages may appear on the same page. Capture that page at each relevant stage. For a **stepper checkout**, capture the corresponding steps. Keep the screenshots in order and use the checkout design donors will actually see. ### Screenshot tips * Coordinate the test flow with WeGive so you can collect review evidence before customer activation. Google's review process supports a TEST integration; WeGive will confirm the appropriate test setup. See the [Google integration checklist](https://developers.google.com/pay/api/web/guides/test-and-deploy/integration-checklist). * Use clear image files accepted by the upload control, such as PNG or JPEG. The Console captured for this guide shows a **1 MB maximum**; keep each file within the displayed limit. * Keep the donation amount, Google Pay button, and relevant page content readable. Use test donor details where possible. * If your device blocks screenshots of the Google Pay window, the Console allows a photo taken with another device. * The Console also permits an error screenshot for the **Google Pay API payment screen** slot. If that is what you see, send it to WeGive for help. It does not demonstrate a successful donation and should not replace the confirmation screenshot. * Use **View examples** in the form for Google's current visual examples. If a required screen is unavailable, ask WeGive for help gathering appropriate evidence before submitting. Upload the matching image into each slot. For another domain, use screenshots that accurately represent that domain's checkout and branding. ## 5. Save and submit each website 1. Review the Website URL, Gateway selection, and uploaded images. 2. Click **Save**. 3. Review any feedback Google displays. Its automatic screenshot check may suggest changes. 4. Click **Submit for approval** when the submission is ready. 5. Return to **Google Pay API → Integrations** and repeat the process for every remaining checkout domain. Saving a draft does not submit it. Automatic screenshot feedback is an initial check; Google's review determines approval. See [Google's submission instructions](https://developers.google.com/pay/api/web/guides/test-and-deploy/publish-your-integration#integrate-your-website). ## 6. Track Google's review Monitor the email address associated with your Console account and check each website entry. * **Active:** Google has approved the integration. * **Needs More Info:** Open Google's email, make the requested changes, and resubmit. * If the entry is still awaiting review, wait for Google's result before requesting activation for that domain. If you need help with Google's feedback, share it with WeGive or use support in the Console. These statuses and the email review process are described in [Google's FAQ](https://developers.google.com/pay/api/faq). Keep track of each domain separately. Approval for one entry does not approve all entries. ## 7. Send your merchant ID and approvals to WeGive Find **Merchant ID** on the Console Dashboard or in the business selector at the top of the page. Copy the Google merchant ID belonging to your organization. Send your WeGive contact: ```text theme={null} Organization name: Google Pay merchant ID: Google Console contact email: Checkout domains and their Google review status: - Domain: Status: Checkout URL: Attached: Google's approval email or screenshots showing the approved entries. ``` WeGive needs your Google merchant ID and the approved domain list. You can share these without sharing your Google account password. WeGive configures Google Pay on WeGive's side using the information you send above — there is no self-service setup step for your organization to complete in the WeGive dashboard. Once WeGive confirms your organization's Google Pay merchant ID and approved domains are on file, WeGive will enable Google Pay for the checkouts you agree on and confirm with you before launch. ## Completion checklist * [ ] The organization's Business Profile is approved. * [ ] Every required checkout hostname has its own submitted website entry. * [ ] Each entry uses **Gateway** and has the requested donation screenshots. * [ ] Google has approved each domain intended for launch. * [ ] WeGive has the organization's Google merchant ID and approval evidence. * [ ] WeGive has confirmed setup, checkout settings, and launch verification. For an additional checkout domain later, repeat the website submission and approval steps, then let WeGive know before offering Google Pay there. ## Related Documentation * [Connecting a Payment Processor](/external/support/settings/connecting-a-payment-processor) — covers the Stripe-connected Google Pay path, a separate setup from this one This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.