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

# Paying by card

> Card, Apple Pay and Google Pay — how it works, and where it doesn't.

There are two routes. One works everywhere; the other is quicker but narrower.

## The onramp — works on everything

<Steps>
  <Step title="Pay by card">
    Card, Apple Pay or Google Pay.
  </Step>

  <Step title="You get USDC">
    Into the wallet you're connected with.
  </Step>

  <Step title="It's swapped">
    To whatever coin you need.
  </Step>

  <Step title="You buy as normal">
    Every mint and purchase runs exactly as it would have.
  </Step>
</Steps>

Works on all eight chains and every collection, because by the time you're
buying, you simply have funds.

The NFT goes to the wallet you signed in with. Never one taken from the request
— which is what stops a stolen card delivering to a stranger's address.

## Direct card checkout — only some listings

Some purchases skip the onramp entirely.

|                             | One-step card checkout |
| --------------------------- | :--------------------: |
| OpenSea listings            |            ✅           |
| Magic Eden listings         |            ✅           |
| **EXC's own listings**      |            ❌           |
| **Minting a v3 collection** |            ❌           |

### Why EXC listings can't

They settle through an escrow wallet rather than an open order book, so there's
nothing on-chain for a payment provider to fill. It's structural, not a missing
integration.

### Why minting can't

The mint function credits whoever submitted the transaction, and checks
allowlists, gates and caps against them. So a provider minting for you ends up
holding the NFT, and a gated phase rejects it outright.

A newer contract that mints to a named recipient is written and tested, but it's
unaudited and not in the launch wizard yet. Collections already on v3 won't be
able to do this regardless.

In both cases you fall back to the onramp, which works fine. It's one extra
step, not a blocked purchase.

## Apple Pay on a shop's own domain

Apple needs a verification file at `/.well-known/`, which we serve. If Apple Pay
doesn't appear on a custom domain, that file failing to load is the first thing
to check.

## If you don't see a card option

Card payment depends on configuration being in place. Where it isn't, the option
doesn't appear at all — you won't get halfway through and hit a failure.