Skip to main content
Darwin Pay is the payment orchestration layer for an Action. It binds a payment to the exact merchant, amount, currency, terms, capability revision, and interaction the user reviewed.
Payment APIs described on this page are a planned preview. They are not available in the production API or MCP tool set yet.

Choose the payment path

Darwin reads the bound payment interaction and exposes only compatible choices. Your product does not translate payment protocols or move credentials through model context.

Direct checkout

Hand the user to the merchant or payment provider and resume the same Action after backend confirmation.

Darwin Pay

Let Darwin coordinate a supported tokenized or protocol-native payment without becoming merchant of record.

Agent wallets

Use a policy-constrained wallet, including a supported Privy wallet, for an eligible onchain payment route.
Use Saved methods for one-time and reusable processor references, Agentic protocols for UCP, ACP, and MPP, or x402 for an HTTP-native payment challenge.

Follow the payment interaction

Darwin can route to a provider’s direct checkout or coordinate a compatible payment through Darwin Pay. Depending on the selected capability, that can include hosted checkout, scoped payment tokens, Link-compatible payment methods, UCP, ACP, MPP, or x402. Darwin does not charge a transaction fee, hold a customer balance, or become merchant of record. The seller or payment provider remains responsible for the commercial transaction.

Submit a bound payment choice

The planned pay_action operation accepts only a route and credential source. Price and merchant fields are deliberately absent because they come from the current interaction.
For a one-time method, Darwin returns a first-party webLink when browser entry is required. Raw card numbers, security codes, bank credentials, private keys, and payment proofs never belong in prompts, tool arguments, or your backend request.

Save a payment method safely

A saved payment method is a revocable processor token or reference. Darwin does not store raw card data. Saving requires explicit user consent and does not authorize future purchases; every payment remains bound to its own interaction and approval policy.

Confirm completion from the Action

Do not treat a redirect, popup closure, wallet signature, or provider message as success. Read the same actionId until Darwin reports a backend-confirmed state. Changed merchant, amount, currency, cart, fees, delivery terms, or expiry invalidate the previous review. Continue with Approve when the payment also requires a consequential user decision.
Last modified on September 22, 2026