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

# Darwin Pay

> Coordinate a bound payment across compatible providers and payment protocols.

Darwin Pay is an orchestration layer, not a wallet or merchant. It chooses a compatible route from the current payment interaction and keeps credentials outside prompts and tool arguments.

## What Darwin Pay coordinates

Darwin Pay can connect a reviewed Action to hosted checkout, Link-compatible methods, scoped payment tokens, saved processor references, policy-constrained [agent wallets](/docs/act/payments/agent-wallets), UCP, ACP, MPP, or x402 when the merchant and provider support them.

```text theme={null}
bound interaction -> compatible route -> tokenized authorization
                  -> provider or merchant confirmation
                  -> current Action state
```

The merchant, amount, currency, protocol, and scope come from the interaction. A client can choose among offered routes but cannot override the commercial terms in the Pay request.

## What Darwin Pay does not do

* Darwin charges no transaction fee and holds no customer balance.
* Darwin does not become merchant of record.
* Darwin never puts raw card details, bank credentials, wallet keys, or reusable payment tokens in model context.
* Authentication to a provider does not grant payment authority or approve changed terms.

Continue with [Saved methods](/docs/act/payments/saved-methods) or [Agentic protocols](/docs/act/payments/agentic-protocols) for the route-specific behavior.