# Activate Google Pay™ (API)

> Enable seamless Google Pay checkout experiences with API-driven setup. Register domains, cascade configurations, and activate Google Pay to tap into millions of saved cards worldwide

<AudienceInfo audiences={['developers']} />

Payabli has simplified the process of getting ready to accept Google Pay. You don't need to create your own Google developer account, encryption keys, certificates, or merchant identifiers.

This guide walks through how to enable Google Pay for your organization via the API.

Enabling Google Pay via the API has several steps.

1. Add the domain.
2. Cascade the domain.
3. Activate the Google Pay service for your org.

The following sections go over each step in detail.

## Add payment method domains

Payment method domains are the web domains where you can accept Google Pay payments. Payabli needs to know which payment domains should accept Google Pay payments to mitigate risk and make sure that transactions are coming from known websites. Managing your payment method domains involves configuring them in Payabli.

To add a domain via the API, make a POST request to the [/PaymentMethodDomain](/developers/api-reference/paymentmethoddomain/paymentmethoddomain-add) endpoint.

<EndpointRequestSnippet endpoint="POST /PaymentMethodDomain" example="Paypoint" />

<Note>
  The domain must be public. It can't be `localhost`, hidden by a VPN, or protected by a password.
</Note>

### Payment method domain examples

The following example walks through the general structure of payment method domains.

Pretend that you own the domain *example.com*, and you want to accept Google Pay on a number of different pages on your various subdomains. You must set up payment method domains for each of your target domains and subdomains.

| Page URL                                                                                                    | Payment Method Domain                                      |
| ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| https:{/* break link */}//www{/* break link */}.{/* break link */}example.{/* break link */}com/monthlydues | www{/* break link */}.example.{/* break link */}com        |
| https\://{/* break link */}subdomain1{/* break link */}.example{/* break link */}.com/payments              | subdomain1{/* break link */}.example.{/* break link */}com |
| https\://{/* break link */}subdomain2{/* break link */}.example{/* break link */}.com/donations/pay         | subdomain2{/* break link */}.example.{/* break link */}com |
| https\:/{/* break link */}/subdomain3{/* break link */}.example{/* break link */}.com/order                 | subdomain3{/* break link */}.example.{/* break link */}com |

## Cascade domains

You have the option to cascade domains. When you cascade a domain, all of the organization's children, including suborganizations and paypoints, inherit the domain. This reduces future operational overhead by automatically adding verified domains to all new suborganizations and paypoints. Payabli strongly recommends cascading domains.

Cascade a domain via the API by sending a POST request to [/PaymentMethodDomain/\{domainId}/cascade](/developers/api-reference/paymentmethoddomain/paymentmethoddomain-cascade).

<EndpointRequestSnippet endpoint="POST /PaymentMethodDomain/{domainId}/cascade" example="CascadeDomain" />

You can run a GET request to [/PaymentMethodDomain/\{domainId}](/developers/api-reference/paymentmethoddomain/paymentmethoddomain-get) to check the cascade status.

The `cascades.jobStatus` field indicates whether the cascade process is complete, failed, or in progress.

```json {5}
 // response truncated 
    "cascades": [
      {
        "jobId": "550139",
        "jobStatus": "completed",
        "jobErrorMessage": null,
        "createdAt": "2024-09-05T14:13:54.698Z",
        "updatedAt": "2024-09-05T14:13:54.698Z"
      }
    ],
```

<Note>
  Payabli recommends a 10 second polling interval when checking domain cascade status.
</Note>

## Activate Google Pay

To activate Google Pay for an organization, make a POST request to the [/Wallet/googlepay/configure-organization](/developers/api-reference/wallet/googlepay/googlepay-configure-organization).

In the body, send `isEnabled` as `true` to activate the Google Pay for the organization. Send `cascade` as `true` to activate Google Pay for the organization's children (including suborganizations and paypoints).

<EndpointRequestSnippet endpoint="POST /Wallet/googlepay/configure-organization" example="ConfigureOrganization" />

After you've sent the activation request, Payabli will enable the service and cascade the settings, if applicable. This can take a few minutes, depending on how your entities are structured.

To check whether Google Pay is activated, send a GET request to [/api/Organization/settings/\{orgId}](/developers/api-reference/organization/get-organization-settings). Check the response for `forWallets`, when Google Pay is active, you'll see the following in the response:

```json
 "forWallets": [
    {
      "key": "IsGooglePayEnabled",
      "value": "true",
      "readOnly": true
    }
  ]
```

## Related resources

See these related resources to help you get the most out of Payabli.

<AccordionGroup>
  <Accordion title="Prerequisites">
    * **[Google Pay™ overview](/guides/pay-in-wallets-google-pay-overview)** - Learn about using Google Pay with Payabli
  </Accordion>

  <Accordion title="Next steps">
    * **[Manage Google Pay™ (API)](/guides/pay-in-developer-wallets-google-pay-manage)** - Learn about managing Google Pay and payment method domains via the Payabli API
  </Accordion>
</AccordionGroup>