> For the complete documentation index, see [llms.txt](https://plexo.gitbook.io/rest-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plexo.gitbook.io/rest-api/core-concepts/digital-wallets.md).

# Digital Wallets

Digital wallets provide a secure, convenient way for customers to pay using their mobile devices. Plexo supports **Google Pay** and **Apple Pay** as payment sources.

## Benefits

| Benefit               | Description                                          |
| --------------------- | ---------------------------------------------------- |
| **Higher Conversion** | Faster checkout with pre-stored payment credentials  |
| **Enhanced Security** | Tokenized card data with device-level authentication |
| **Reduced PCI Scope** | Card details never touch your servers                |
| **Better UX**         | One-tap payments with biometric authentication       |

## Supported Digital Wallets

| Wallet         | Platforms             | Auth Methods                 |
| -------------- | --------------------- | ---------------------------- |
| **Google Pay** | Android, Web (Chrome) | `CRYPTOGRAM_3DS`, `PAN_ONLY` |
| **Apple Pay**  | iOS, macOS, Web       | Network Token + Cryptogram   |

## How It Works

Digital wallet payments follow a secure token-based flow:

1. **Customer Authentication** - Customer authenticates with their device (Face ID, fingerprint, PIN)
2. **Token Generation** - Wallet SDK generates an encrypted payment token
3. **Token Transmission** - Your app sends the token to your server
4. **Payment Processing** - Your server forwards the token to Plexo API
5. **Decryption & Processing** - Plexo decrypts and processes the payment
6. **Confirmation** - Payment result returned to your app

This approach ensures that sensitive card data never touches your servers, significantly reducing your PCI compliance scope.

## Comparison

| Feature          | Google Pay                             | Apple Pay                  |
| ---------------- | -------------------------------------- | -------------------------- |
| **Platforms**    | Android, Web                           | iOS, macOS, Web            |
| **Auth Methods** | CRYPTOGRAM\_3DS, PAN\_ONLY             | Network Token + Cryptogram |
| **3DS**          | Pre-authenticated when CRYPTOGRAM\_3DS | Pre-authenticated          |

## Getting Started

1. Log in to the **Plexo Dashboard**
2. Navigate to **Integrations**
3. Contact `soporte@plexo.com.uy` to enable Google Pay for your merchant, or enable Apple Pay
4. For Apple Pay, upload your Payment Processing Certificate

## Next Steps

* [Google Pay Integration Guide](/rest-api/wallets/google-pay.md) - Complete setup and integration instructions
* [Apple Pay Integration Guide](/rest-api/wallets/apple-pay.md) - Complete setup and integration instructions
* [Apple Pay Certificate Setup](/rest-api/wallets/apple-pay/apple-pay-certificate-setup.md) - Step-by-step certificate generation
* [Wallet Integrations API Reference](/rest-api/api-reference/wallet-integrations.md) - Full API documentation


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://plexo.gitbook.io/rest-api/core-concepts/digital-wallets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.