# Trading

## Swap

Core Web's swap aggregates quotes across integrated liquidity sources on the
active network and executes against the best one. For token teams, no
listing step is involved beyond being tradable on an integrated venue —
if your pool has liquidity, the aggregator can route to it.

Approvals follow the standard ERC-20 pattern: the swap prompts for an
allowance to the router when needed, and users can audit and revoke those
later with the [revoke-access tool](/docs/core-web/tools).

## Recurring swaps

Users can schedule a swap to repeat — a dollar-cost-averaging primitive.
Each execution is a real on-chain swap from the user's account, visible in
[activity](/docs/core-web/portfolio) like any other transaction.

## Buying with fiat

Fiat on-ramping runs through [Meld](https://meld.io/), which routes across
payment providers (cards, bank transfer, Apple Pay and Google Pay where
available). The provider handles KYC; purchased assets land in the user's
account as normal on-chain transfers.

## For dapp developers

None of this replaces your own integration — a dapp that wants to swap
programmatically uses its own routing and requests signatures through the
[provider API](/docs/reference/provider-api). The trading surface is what
*users* do inside Core; the on-chain effects (allowances to routers, swap
transactions) are standard and visible to any indexer.