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

# Payment Methods

> Understanding the payment methods available for onramp

Crossmint Onramp lets users buy stablecoins with the payment methods they already have: debit and credit cards, Apple Pay, and Google Pay. This page explains how each method works, where it is available, and why an onramp transaction is different from a token checkout.

## Supported Payment Methods

| Method         | Description                                          | Availability                                               |
| :------------- | :--------------------------------------------------- | :--------------------------------------------------------- |
| **Card**       | Debit and credit cards (Visa, Mastercard)            | All platforms                                              |
| **Apple Pay**  | One-click payment with cards stored in Apple Wallet  | Safari on macOS and iOS (web), native iOS apps             |
| **Google Pay** | One-click payment with cards stored in Google Wallet | Web browsers, Android apps (React Native, Flutter, Kotlin) |

All three methods are selected by the user inside the same embedded checkout component. You control which methods are offered through a single configuration option (`allowedMethods`), and the component only displays the methods that the user's device and browser actually support. For example, Apple Pay is never shown on an Android device, even when it is enabled.

## How Each Method Works

### Card

The user enters their card details directly in the embedded checkout. Card data is captured in a PCI-compliant environment and never touches your servers. Cards are the baseline method: they work on every platform without additional configuration.

### Apple Pay

Apple Pay wraps the user's stored cards behind Face ID, Touch ID, or a device passcode. Instead of typing card details, the user confirms the payment through the native Apple Pay sheet.

Apple requires every web domain that displays the Apple Pay button to be verified with Apple. Crossmint manages the Apple merchant relationship, so you only need to verify your domain once through the Crossmint Console. Native iOS apps do not require domain verification; the Swift SDK supports Apple Pay automatically.

### Google Pay

Google Pay works the same way for cards stored in Google Wallet: the user confirms the payment through the native Google Pay sheet instead of typing card details.

On the web, Google Pay works without additional configuration. Mobile apps require native configuration (permissions and intent declarations) because the payment sheet is rendered by the operating system, and production Android apps must be approved by Google before Google Pay is shown to real users.

## Why Onramp Is Not a Standard Checkout

A standard card payment in a checkout pays for a good or service; the cardholder receives a product, and the transaction ends there. An onramp transaction is different: the user's fiat is converted into stablecoins that are delivered to a wallet. This is a **regulated transfer** — a money movement that must run on licensed infrastructure.

Because of this, every onramp transaction is routed through Crossmint's regulated infrastructure, which handles:

* **Licensing** — Crossmint operates the required licenses, so you do not need your own.
* **Identity verification** — users complete a lightweight KYC once, valid for up to \$1,000 per day. See [User Onboarding](/onramp/introduction/user-onboarding).
* **AML screening and sanctions checks** — every transaction is screened before the stablecoins are delivered.
* **Chargeback liability** — Crossmint assumes liability for fraudulent disputes.

The payment method only changes how the user funds the transaction. Whether they pay with a card, Apple Pay, or Google Pay, the compliance flow and the on-chain delivery are identical.

<Info>
  The user experience differs mainly in friction: Apple Pay and Google Pay skip manual card entry and typically convert better on mobile devices, while cards remain the universal fallback.
</Info>

## Choosing Which Methods to Offer

Offering every method is usually the right default: the checkout only shows what the device supports, so enabling all three costs nothing. Restricting methods makes sense when:

* Your app is native-only on one platform and you want to hide methods that will never appear.
* You have a business reason to route users through a specific method.

## See Also

<CardGroup cols={2}>
  <Card title="Add Payment Methods" icon="credit-card" href="/onramp/guides/payment-methods">
    Enable Apple Pay, Google Pay, and cards in your integration
  </Card>

  <Card title="User Onboarding" icon="id-card" href="/onramp/introduction/user-onboarding">
    How identity verification works for onramp
  </Card>
</CardGroup>