> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/integrations/universal-channel/how-to-manage-mobile-wallets.md).

# How to manage mobile wallets?

Understand mobile wallet passes and how to manage them with Batch.

## What are mobile wallets?

Mobile wallets store digital payment cards and passes on a smartphone.

Apple Wallet and Google Wallet are common examples. Beyond payments, wallets can hold loyalty cards, coupons, boarding passes, tickets, and membership cards.

Wallet passes give customers a convenient, always-available version of these items. They can also display timely updates, such as a changed balance or offer.

## How does Batch support mobile wallets?

Batch manages wallet interactions through [Universal Channel](/getting-started/features/customer-engagement-platform/message/universal-channel.md).

From a trigger automation, Batch sends a personalized `POST` request to your wallet provider's API. The provider then creates, updates, or distributes the wallet pass.

For example, Batch can trigger a wallet provider to:

* issue a loyalty card after registration;
* update points or membership status after a purchase;
* send a new offer to eligible customers.

Batch does not create or host wallet passes itself. A wallet provider, such as [The Wallet Crew](https://www.thewalletcrew.io/en), handles the pass lifecycle.

{% hint style="info" %}
Universal Channel is a paid offering. Contact your CSM or Account Manager to enable it.
{% endhint %}


---

# 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://doc.batch.com/integrations/universal-channel/how-to-manage-mobile-wallets.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.