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.
Follow the payment interaction
Submit a bound payment choice
The plannedpay_action operation accepts only a route and credential source. Price and merchant fields are deliberately absent because they come from the current interaction.
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 sameactionId 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.