> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/apple-and-google-wallet.md).

# Apple & Google Wallet

Configure Apple Wallet and Google Wallet securely, with brand-owned credentials for compliance.

The Wallet Crew generates passes for Apple Wallet and Google Wallet on behalf of the brand. Apple and Google enforce strict issuer identity, signing, and data-handling rules. This setup is critical for compliance and security. The brand must use brand-owned Apple and Google issuer accounts and credentials.

The brand sets up and controls the accounts and credentials needed to issue passes (certificates, keys, issuer IDs, and approvals). The Wallet Crew uses brand-provided values to sign and manage passes securely. This keeps the brand as the issuer of record and reduces credential risk. The Wallet Crew acts as the technical provider.

In practice, the brand's Legal & IT teams manage the “issuer side” configuration. This includes account ownership, issuer identifiers, signing credentials, and provider approvals. The brand can rotate or revoke credentials at any time. The Wallet Crew should not be the long-term owner of issuer credentials.

{% hint style="warning" %}
This configuration keeps the brand in control of issuer identity and pass data. It also increases security by avoiding third-party ownership of signing keys and provider accounts, and by enabling brand-managed rotation and revocation.
{% endhint %}

Security teams at the brand can review the platform security model in [Wallet card security](/configure/advanced-configuration/wallet/wallet-card-security.md).

### What happens during the onboarding process

* The brand completes the required Apple and Google setup under brand accounts.
* The brand shares the required identifiers and credentials in the admin console.
* The Wallet Crew verifies the setup matches Apple and Google requirements.
* The Wallet Crew confirms readiness for pass generation and testing.

### More information

Use the platform-specific setup guides below

* Apple: create and manage certificates and push keys : [Apple Wallet certificates](/configure/advanced-configuration/wallet/apple-and-google-wallet/apple-wallet-certificates.md)
* Google: set up the issuer account and required credentials : [Google Wallet account](/configure/advanced-configuration/wallet/apple-and-google-wallet/google-wallet-account.md)

### FAQ

<details>

<summary><strong>Can a brand go live with only Apple Wallet or only Google Wallet?</strong></summary>

**No**. The brand needs to configure both Apple Wallet and Google Wallet before going live, so the program covers both iOS and Android customers from day one.

</details>

<details>

<summary><strong>Can The Wallet Crew configure Apple/Google for a brand (delegated access)?</strong></summary>

**Yes**. Brands can grant temporary admin access in the provider portals, delegate the configuration to The Wallet Crew, and remove admin access after validation. The brand remains the owner of the accounts and credentials.

</details>

<details>

<summary><strong>How long does setup take?</strong></summary>

It depends on organization size and whether the brand already owns Apple and Google accounts. Configuration takes around **15 minutes to 1 hour** per wallet provider.

</details>

<details>

<summary><strong>Can a brand rotate or revoke credentials? What happens to existing passes?</strong></summary>

**Yes**. The brand can rotate or revoke credentials at any time. If credentials are revoked, issuance and updates can stop until they are replaced, and installed passes may stop updating.

</details>

<details>

<summary><strong>Should the brand configure both staging and production?</strong></summary>

**No**. The brand can configure only one environment to start. The Wallet Crew can replicate configuration changes on demand.

</details>

<details>

<summary><strong>Does the brand need all information before starting the project?</strong></summary>

**No**. The Wallet Crew can provide test credentials to configure and set up the platform while the brand team completes the configuration.

These credentials **can’t be used in production**. They are for testing only.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/apple-and-google-wallet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.