> ## Documentation Index
> Fetch the complete documentation index at: https://docs.methodfi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Commerce

> Connect customers' credit cards, reduce failed payments, and personalize customer experiences with Method's Commerce APIs.

## What This Section Covers

Learn how to use Method's Commerce APIs to:

* **Connect every credit card** a customer owns in a single flow.
* **Evaluate payment readiness** before authorizing a transaction.
* **Retry failed payments at the optimal time** to improve recovery.
* **Personalize customer experiences** using wallet intelligence.

Whether you're building a wallet, improving payment success, or personalizing customer experiences, every Commerce integration follows the same core workflow.

```mermaid theme={null}
flowchart TD
    A[Create Entity] --> B[Verify Identity]
    B --> C[Connect Credit Cards]
    C --> D[Wallet Onboarding]
    C --> E[Preauth Signals]
    C --> F[Wallet Intelligence]
    style C fill:#00B29D,color:#fff
```

## Commerce Use Cases

| Use case | Core endpoints | Use when you want to |
| - | - | - |
| [**Wallet Onboarding**](https://docs.methodfi.com/guides/use-cases/commerce/wallet-onboarding.md) | Entity-Connect, Card Brand, Payment Instruments | Reduce onboarding friction by letting customers connect all their credit cards in one flow |
| [**Preauth Signals**](https://docs.methodfi.com/guides/use-cases/commerce/preauth-signals.md) | Entity-Connect, Preauth Signals | Increase payment success by evaluating payment readiness before authorization and retrying failed payments at the optimal time |
| [**Wallet Intelligence**](https://docs.methodfi.com/guides/use-cases/commerce/wallet-intelligence.md) | Entity-Connect, Attributes | Personalize offers and product experiences based on customers' credit cards |

## Two Integration Paths

> [tab] API-Only
>
> Integrate directly with Method's APIs for entity creation, identity verification, Connect, and all downstream card operations. You build the user-facing flow and have full control over the UX.
>
> PCI compliance is not required: by default, tokenization returns network tokens that don't expose raw card credentials.

> [tab] Embedded UI (Opal)
>
> Use [Opal Card Connect](https://docs.methodfi.com/opal/card_connect/overview.md) as a drop-in UI for identity verification and card discovery. Opal handles the user-facing flow while you use the API for card brand enrichment, payment instruments, and wallet attributes.

## Get Started

> [card] [Getting Started](https://docs.methodfi.com/guides/use-cases/commerce/getting-started.md)
>
> The 3-step setup: create an entity, verify identity, and connect credit cards.

> [card] [Wallet Onboarding](https://docs.methodfi.com/guides/use-cases/commerce/wallet-onboarding.md)
>
> Connect every credit card without manual entry, then enrich and tokenize for checkout.

> [card] [Preauth Signals](https://docs.methodfi.com/guides/use-cases/commerce/preauth-signals.md)
>
> Evaluate payment readiness before authorization and optimize payment retries.

> [card] [Wallet Intelligence](https://docs.methodfi.com/guides/use-cases/commerce/wallet-intelligence.md)
>
> Retrieve wallet-level insights to personalize customer experiences.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.