# Requesting access

To access restricted sections of our Device Tokenization documentation, you must be signed
into a Google Account that's been authorized to view that content. Partners must use a Google
Account associated with their corporate email address rather than a personal account.

- If [Google Workspace](https://gsuite.google.com/) hosts your corporate account, you already have a Google account.
- If your email is hosted through another provider, [Create
  your Google Account](https://accounts.google.com/SignUpWithoutGmail) using your corporate email address.

Once you have created your Google account, you are ready to request access using
[this
form](https://support.google.com/faqs/contact/google_pay_issuer_allowlist). If you have a profile within [Issuer Console](https://pay.google.com/business/console?business_type=financial_institution), you can gain access by submitting your email within the
Console using the instructions provided on the [Get Started page](https://developers.google.com/pay/issuers/overview/get-started#4_access_push_provisioning_api_documentation).
Console will grant you immediate access to the documentation without further delay.

> [!NOTE]
> **Note:** This content is intended for card issuing financial institutions that have a signed contract to integrate with Google Pay. If you are a merchant, you should refer to the [merchant documentation](https://developers.google.com/pay/) instead.

## Common questions:

1. If you are have trouble accessing the site but have already been granted access, try clicking the ["Sign in"](https://accounts.google.com/AccountChooser?continue=https://developers.google.com/pay/issuers) button displayed to unauthorized users to either log into or select the authorized Google account.
2. If you are a Google Workspace user, check that your administrator has enabled Google Developers for your domain as described in this [support
   article](https://support.google.com/a/answer/10621196).